System and method for establishing communication channels between on-board unit of vehicle and plurality of nodes

ABSTRACT

A method includes establishing communication channels between an on-board unit (OBU) of a vehicle and a plurality of nodes, tagging each of a plurality of data from the plurality of nodes with a priority level, storing the plurality of data in a priority queue according to respective priority levels, selecting a medium to present a first data of the plurality of data to a user, and presenting the first data to the user via the medium. In the method, the plurality of nodes includes a remote node and an in-vehicle device. Another method includes receiving a data from a remote node, generating a plurality of data streams from the data and transmitting the plurality of data streams across a plurality of wireless interfaces. Another method includes enhancing audio signals from a plurality of microphones and speakers. Yet another method includes various gesture based user interfaces coupled to the OBU.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of priority under 35 U.S.C. §119(e)of U.S. Provisional Application Ser. No. 61/433,138, filed Jan. 14,2011, by Sateesh K. Addepalli et al., entitled “SYSTEM, METHOD, ANDPROCESSES ASSOCIATED WITH CONNECTED VEHICLES,” which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

This disclosure relates in general to the field of electroniccommunications and, more particularly, to real-time synthesis andperformance enhancement of audio/video data, and noise cancellation andgesture based user interfaces in a vehicular environment.

BACKGROUND

Networking architectures have grown increasingly complex, and further,have been designed for use in a wide variety of communicationsenvironments. Demand continues to rise among the subscriber base of endusers for network access across diverse network environments. Inparticular, configuring suitable network architecture for vehicularenvironments (e.g., automobiles, buses, airplanes, trains, boats, etc.)presents unique difficulties. Vehicles can be mobile across a largegeographic area, can travel at variable speeds, can have internalnetworks related to the vehicle itself, and can include more than oneend user at a time. Providing the ability to synthesize and enhance theperformance of audio-visual data, and to offer noise cancellation andgesture based user interfaces in the vehicular environment presentssignificant challenges to system designers, vehicle manufacturers andthe like.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure andfeatures and advantages thereof, reference is made to the followingdescription, taken in conjunction with the accompanying figures, whereinlike reference numerals represent like parts, in which:

FIG. 1 is a simplified block diagram of one embodiment of acommunication system in accordance with the present disclosure;

FIG. 2 is a simplified schematic diagram of the communication system inexemplary network environments associated with embodiments of thepresent disclosure;

FIG. 3 is a simplified block diagram of the communication systemaccording to embodiments of the present disclosure;

FIG. 4 is a simplified flow chart illustrating example operations thatmay be associated with a method for real time synthesis of dataaccording to embodiments of the present disclosure.

FIG. 5 is a simplified block diagram illustrating additional details ofthe communication system according to embodiments of the presentdisclosure.

FIG. 6 is a simplified block diagram of potential components in thecommunication system according to embodiments of the present disclosure.

FIG. 7 is a simplified flow chart illustrating example operations thatmay be associated with a method for performance enhancement of dataaccording to embodiments of the present disclosure;

FIG. 8 is a simplified flow chart illustrating further exampleoperations that may be associated with a method for performanceenhancement of data according to embodiments of the present disclosure;

FIG. 9 is a simplified flow chart illustrating example operations thatmay be associated with a method for performance enhancement of dataaccording to another embodiment of the present disclosure;

FIG. 10 is a simplified flow chart illustrating example operations thatmay be associated with a method for performance enhancement of dataaccording to yet another embodiment of the present disclosure;

FIG. 11 is a graph of quality versus rate for two potential data flowsin accordance with embodiments of the present disclosure;

FIG. 12 is a simplified diagram illustrating a potential principle ofoperation of the communication system according to an embodiment of thepresent disclosure;

FIG. 13 is a simplified flow chart illustrating example operations thatmay be associated with a method for performance enhancement of dataaccording to yet another embodiment of the present disclosure;

FIG. 14 is a simplified block diagram illustrating a potential principleof operation of performance enhancement of data according to anembodiment of the present disclosure;

FIG. 15 is a simplified block diagram illustrating a potential principleof operation of performance enhancement of data according to anotherembodiment of the present disclosure;

FIG. 16 is a simplified flow chart illustrating example operations thatmay be associated with a method for performance enhancement of dataaccording to yet another embodiment of the present disclosure;

FIG. 17 is a simplified block diagram of example components of thecommunication system according to embodiments of the present disclosure;

FIG. 18 is a simplified flow chart illustrating example operations thatmay be associated with a method for noise cancellation according to anembodiment of the present disclosure;

FIG. 19 is a block diagram illustrating example components of thecommunication system according to embodiments of the present disclosure;

FIG. 20 is a simplified diagram illustrating example user interfacesaccording to embodiments of the present disclosure;

FIG. 21 is a simplified flow chart illustrating example operations thatmay be associated with a method using user interfaces according toembodiments of the present disclosure;

FIG. 22 is a simplified diagram of example components of thecommunication system according to embodiments of the present disclosure;

FIG. 23 is a simplified diagram of a user interacting with examplecomponents of the communication system according to another embodimentof the present disclosure;

FIG. 24 is a simplified diagram of example components of thecommunication system according to embodiments of the present disclosure;

FIG. 25 is a simplified flow chart illustrating example operations thatmay be associated with an example scenario with user interfacesaccording to embodiments of the present disclosure;

FIG. 26 is a simplified flow chart illustrating further exampleoperations that may be associated with another example scenario withuser interfaces according to embodiments of the present disclosure;

FIG. 27 is a simplified flow chart illustrating additional exampleoperations that may be associated with yet another example scenario withuser interfaces according to embodiments of the present disclosure; and

FIG. 28 is a simplified flow chart illustrating yet other exampleoperations that may be associated a further example scenario with userinterfaces according to embodiments of the present disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

A method according to an example embodiment includes establishingcommunication channels between an on-board unit (OBU) of a vehicle and aplurality of nodes, receiving a plurality of data from the plurality ofnodes, tagging each of the plurality of data from the plurality of nodeswith a respective priority level, storing the plurality of data in apriority queue according to the respective priority levels, selecting amedium to present a first data of the plurality of data to a user, andpresenting the first data to the user via the medium. In the method, theplurality of nodes includes a remote node and an in-vehicle device. Morespecific embodiments include identifying a data type of the first data,accessing a previously stored mapping of data types to correspondingpriority levels, and associating a priority level to the first datawhere the priority level corresponds to the data type of the first data.

A method according to an example embodiment includes establishing acommunication channel between a node and a sender, extracting a metainformation of a data from the sender, calculating a connectivity ofeach wireless interface in a plurality of wireless interfaces,generating a plurality of data streams from the data, and transmittingthe plurality of data streams across the plurality of wirelessinterfaces. More specific embodiments include additional aspectsincluding calculating connectivity of each wireless interface using lossrate and RSSI measurements, matching traffic rate across each wirelessinterface with bandwidth according to media characteristics of the data,calculating retransmission levels, and other features.

A method in another example embodiment includes locating at least twomicrophones and at least two speakers inside a vehicle, wherein themicrophones and speakers are adapted to communicate with the OBU,receiving, on a first microphone, a first audio signal corresponding toa sound from a user, and receiving, on a second microphone, a secondaudio signal corresponding to the sound. The first microphone is locatedcloser to the user than the second microphone. The method includesdetermining a source of the sound from the first audio signal and thesecond audio signal, and enhancing the first audio signal. More specificembodiments include transmitting a third audio signal on the at leasttwo speakers, and enhancing the third audio signal on at least one ofthe at least two speakers and other features.

A method in another example embodiment includes sensing a gesture by auser on a user interface inside a vehicle, interpreting the gesture tocorrespond to a command for an on-board unit (OBU) of a vehicle, andsending controlling signals to an application associated with the userinterface. More specific embodiments include various types of gesturesand user interfaces.

Example Embodiments

Turning to FIG. 1, FIG. 1 is a simplified block diagram of acommunication system 10 for real-time synthesis and performanceenhancement of audio/video data, and noise cancellation and gesturebased user interfaces in a vehicular environment. The examplearchitecture of FIG. 1 includes an end user (driver) 2 operating avehicle 4 that includes an on-board unit (OBU) 30. In this particularexample, OBU 30 includes processing elements 21, which include acomputing processor 22 and a routing processor 23. OBU 30 also includesa memory element 24, network interfaces 26, a user interface 27, and adisplay 28. OBU 30 can be suitably coupled to a plurality of sensors 14a-c, a plurality of controls (e.g., electronic control units (ECUs)) 16a-c, and a plurality of actuators, such as actuator 13. In one exampleembodiment, sensors 14 a-b and controls 16 a-b may be part of anautomotive diagnostic system, indicated by vehicle diagnostics 19, whichmay also be suitably integrated with OBU 30. OBU 30 may also be suitablycoupled to various in-vehicle mobile devices 18 a-b at any given time,where such devices may be associated with particular end users(passengers or driver) within vehicle 4. OBU 30 may also includecapabilities associated with navigation system 17 (e.g., a globalpositioning system (GPS)).

FIG. 1 also includes networks 40, representing various types ofconnectivity to vehicle 4 (e.g., via antenna 29). Each establishednetwork of networks 40 has a logical coupling to remote nodes, which mayinclude transaction systems 50, authorized entities 98, and othervehicles 59. A node may be any electronic device (e.g., machine deviceor a mobile device), client, server, peer, network element, service,application, or other object capable of sending, receiving, orforwarding information over communications channels in a network. Aremote node may be any node located externally to a particular vehicle,such as vehicle 4. Examples of remote nodes include end user devices,mobile devices, electronic devices in networked systems (e.g., server ina datacenter, end user device in a local area network (LAN), etc.), OBUsof other vehicles, and road-side user devices. An end node as usedherein, encompasses nodes that originate data packets in a network flow,and nodes that are the final destination of the data packets in thenetwork flow. For example, sensor 14 a and authorized entities 98 may beend nodes in a network flow, wherein sensor 14 a originates data packetsto send to authorized entities 98.

Elements of FIG. 1 may be coupled to one another through one or moreinterfaces (e.g., network interfaces 26) employing any suitable link(wired or wireless), which provides a viable pathway for electroniccommunications. Additionally, any one or more of these elements may becombined or removed from the architecture based on particularconfiguration needs. Communication system 10 may include a configurationcapable of transmission control protocol/Internet protocol (TCP/IP)communications for the electronic transmission or reception of packetsin a network. Communication system 10 may also operate in conjunctionwith a user datagram protocol/IP (UDP/IP) or any other suitableprotocol, where appropriate and based on particular needs. In addition,communication system 10 may also include a configuration capable ofaccommodating legacy bus subsystems that may be employed to conveyinformation across the myriad of machine devices (e.g., sensors 14 a-c,controls 16 a-c, actuator 13) in vehicle 4. A ‘subsystem’ as used hereinis intended to encompass a network within a vehicle, where the networkis a collection of nodes interconnected by communicative channels thatfacilitate electronic communications therebetween, in which the nodesare integrated with or otherwise linked to the vehicle.

Embodiments of communication system 10 can enable real-time synthesisand performance enhancement of audio/video data, and noise cancellationand gesture based user interface in a vehicular environment. Given theplethora of transaction agents (e.g., machine devices, humans, softwareagents, mobile devices, and authorized entities) and possibletransactions (e.g., accessing one or more wireless/mobile/cellularnetworks and using network bandwidth and services, gaining access tovarious resources of the vehicle based on an identity profile and/orassociated databases, gaining access to transaction applications in thevehicle, and engaging in commercial activities), numerous transactionscenarios may occur over the life of the vehicle. Such transactionscenarios may encompass, for example, toll or parking payments, vehiclemiles traveled (VMT) systems, Internet commerce, original equipmentmanufacturer (OEM), gas and electric charging stations, roadside and/ordrive-through kiosks, banking applications, vehicle dealer systems,location based service (LBS) system, vehicle system and its resources,mobile network operator system, travel agencies, rental and leasingagencies, network connection to Internet sites, vehicle-to-vehiclecommerce, vehicle-to-mobile-device commerce, in-vehicle commercesystems, restaurants, commercial establishments, etc. Accordingly, it isimportant to have a flexible identity and access framework to ensurethat appropriate transactions can be executed by different agents overtime. A unified identity management framework enables aggregation andassociation of these agents and transactions.

Communication system 10 may include on-board unit (OBU) 30 that createsuser profiles for each agent, grants appropriate levels of access,manages potential conflicts (e.g., by assigning priority to differentagents), and provisions the appropriate wireless/mobile connectivity.The agent may be provisioned for authentication and access to aparticular vehicle by provisioning at least one identity profile in OBU30 of communication system 10. The identity profile may include userpreferences such as priorities, most frequently visited Internet sites,gesture based actions, etc. The identity profile may also includeassociations between user gestures and specific transaction applicationscorresponding to the particular transactions. Finally, appropriatewireless/mobile connectivity may be dynamically determined by evaluatingthe transaction, the agent, the identity profile, and a currentgeographical location of the vehicle. Thus, vehicular transactions maybe flexibly enabled by managing the identity of agents associated withtransactions.

Certain terminologies are used with regard to the various embodiments ofthe present disclosure. The term ‘road-side’ as used herein is intendedto mean outside of a vehicle and may or may not be physically located bya road. In addition, ‘user device’ as used herein is intended to includemobile devices, personal computers, electronic devices, and any otherdevice, component, element, or object operable by a user and capable ofinitiating voice, audio, video, media, or data exchanges associated withcommunication system 10. The term ‘road-side infrastructure device’ asused herein includes a base station, access point, satellite, and anydevice capable of facilitating a voice, audio, video, media, or dataexchanges between a user device or OBU and the Internet. As used herein,the term ‘machine device’ is meant to encompass sensors, actuators,vehicle controllers including ECUs, instruments, embedded devices, mediadevices, infotainment systems, vehicle navigation systems, displays,other peripheral or auxiliary devices or components, etc. Machinedevices may be physically distributed across the vehicle in a vehiclesubsystem, consolidated in any way, provisioned in proprietaryconfigurations, or otherwise configured based on particular networking,vehicle, and/or end user needs. The term ‘in-vehicle device’ as usedherein, encompasses machine devices and user devices located inside avehicle. The term ‘link’ as used herein, encompasses a physical orlogical communications channel that connects two or more communicatingdevices. The term ‘channel’ as used herein, encompasses a physicaltransmission medium, such as a wire, or a logical transmission medium,such as a radio channel. The term ‘path’ as used herein encompasseslinks and nodes connecting two end nodes in a network. Otherterminologies are defined throughout the Specification.

For purposes of illustrating certain example techniques of communicationsystem 10, it is important to understand the communications that may betraversing the network. The following foundational information may beviewed as a basis from which the present disclosure may be properlyexplained. Such information is offered earnestly for purposes ofexplanation only and, accordingly, should not be construed in any way tolimit the broad scope of the present disclosure and its potentialapplications.

Many useful, but disparate, networks may exist in today's vehicles. Forexample, a controller-area network (CAN) bus, a geographical positioningsystem (GPS), and personal mobile devices (e.g., mobile phones, smartmobile phones/devices, e-book readers, tablets, laptops/net books,portable navigation systems, multimedia devices, etc.) facilitate thecoexistence of some of the many possible networks within a singlevehicle such as a personal automobile. A CAN bus is a vehicle busstandard designed to allow microcontrollers, sensors, and other devicesassociated with a vehicle to communicate with each other within thevehicle (e.g., without a host computer). CAN is a message basedprotocol, designed for and typically used by automotive applications.With appropriate network access, the CAN bus can be used to providereal-time vehicle diagnostics from associated sensors and controls to amanufacturer of the vehicle or to any other authorized entity. Aseparate network in the vehicle may exist for IP devices involved in thevehicle navigation system (e.g., GPS) and, possibly, another networkassociated with simple content delivery. Other networks could be usedfor Internet access for end users through, for example, mobile devices.Hence, various levels of network usage, different purposes of networkusage, and different agents (e.g., humans, machine devices, externaldevices, mobile devices) associated with the network usage may occur ina single vehicle. Network usage in each of the identified cases may havea different usage scope, different latency, different associatedrouting, different policy requirements, and the like.

External networks may be accessed from a vehicle by certain electronicdevices when a communication link is available. An ‘external network’ asused herein is intended to encompass a network that is external to avehicle, where the network is a collection of nodes interconnected bycommunicative channels that facilitate electronic communicationstherebetween. Mobile devices such as, for example, mobile phones, smartmobile phones/devices, e-book readers, tablets, laptops/net books,portable navigation systems, multimedia devices, other handheld devices,etc. may be used within a vehicle to wirelessly access an externalnetwork, for making a cellular phone call, accessing the Internet via amobile network operator, and accessing the Internet via a WiFi link to aroad-side access point. A vehicle router in a vehicle may also be usedto access a roadside infrastructure device within range of the vehicle.However, external network access from mobile devices and/or vehiclerouters is dependent upon the particular wireless interfaces beingwithin a wireless range of corresponding mobile or wireless networkinfrastructures. If the particular corresponding wireless infrastructuredevices are not within a wireless range, or if the vehicle carrying themobile devices and vehicle routers moves outside of the wireless range,then external network communication can be lost.

Vehicles may be equipped with vehicle navigation systems, for example,GPS. In-vehicle devices, such as cell phones and laptops, may also beequipped with vehicle navigation systems. In such vehicle navigationsystems, information displayed on maps (and used for routing) is largelystatic. Many devices contain navigation data provided by the originalmanufacturer that cannot be changed, while other devices (such asAndroid phones) can connect to the Internet for information updates suchas points-of-interest (POIs) and general traffic congestion data. Whilethere is seemingly infinite information available on the Internet, thevolume of information that is current and updated within a relativelysmall period of time is considerably small. Finding localized, transientgeo-social information, for example, store specials and restaurantqueues in a downtown area on a Tuesday at 11:00 AM, or the location androute of an advancing emergency vehicle, is still very difficult.

Additionally, even if some wireless communication links are available,they may not be desirable for extended use in a mobile vehicle. Forexample, pricing contracts with mobile network operators typicallyprovide cellular coverage through the particular operator for a certainfee based on defined criteria. Example criteria may include tieredpricing on bandwidth usage over 3G/4G/WiFi/Satellite. However, due tocapacity constraints, interference, multipath and other fading relatedissues in a moving vehicle, bandwidth availability may be limited.Additionally, failures in external networks may compromise bandwidthavailability, leading to packet loss and congestion. Even if bandwidthis sufficiently available, a user may want to conserve and maximize theuse of available bandwidth to reduce costs due to tiered pricing onbandwidth. Moreover, a user may access different types of traffic overwireless networks, for example, video, text, binary and audio data. Whenmultiple streams of data containing audio and video are accessed by oneor more users in a connected vehicle, such data streams may compete forthe available limited bandwidth. Performance enhancements of the audioor video data streams in accordance with the embodiments disclosedherein may ensure high quality of the audio/video data streams even withlimited bandwidth.

Video or audio streams transmitted over a wireless channel mayexperience degradation in quality because wireless channels areinherently noisy due to fading, multipath, and shadowing effects, whichcan result in a much higher bit error rate (BER) and consequently a lowthroughput. Many techniques exist to enhance performance of audio/videostreams, for example, compressing and encoding video packets beforetransmission over the wireless channel. These techniques are implementedat the end nodes, and there is no participation by intermediate nodesnot at a network level. For example, adaptive streaming has been used inInternet based video-platforms, where a receiver (i.e., an end node thatis a final destination of data packets in a network flow) observes itslocal buffer status, and dynamically requests a sender (i.e., an endnode that originates data packets in a network flow) for a suitableversion of the encoded video stream, in the attempt to always match theavailable bottleneck bandwidth. The static adaptive streaming systemsare generally designed for end nodes with relatively stable networkconnections (e.g., desktop computers, laptops on home wireless networks,etc.), wherein network conditions may be unlike the network conditionsfor connected vehicular environments with time-varying bandwidth, highpacket loss rates, and highly varying round trip times. Moreover,various schemes exist for unequal error protection for voice or videopackets based on their relative importance, or dispersing packets acrossmultiple available links and/or paths. However, these schemes aretypically applicable to semi-static scenarios without mobility. Incontrast, connected vehicular environments may see highly variablenetwork conditions.

In the connected vehicle environment discussed above, link quality maysuffer even with a single wireless hop because of additional challengesdue to high vehicle speeds, mobility, multiple access technologies,multiple path properties (e.g., for a single TCP connection) and highlydynamic bandwidth/latency scenarios, making it difficult to utilizeavailable bandwidth and achieve reasonable performance. In addition, inthe connected vehicle environment, different classes of traffic (basedon various factors such as user profile, application priority, andpolicy settings) may compete for limited link resources and posedifferent Quality of Service (QoS) requirements. These classes oftraffic originate from devices that may not be tuned to operateoptimally in such challenging wireless conditions. Therefore, there is aneed to optimize bandwidth usage by such devices, for example, byenhancing performance of high priority data streams without additionalbandwidth usage.

Another aspect of a vehicular network environment includes multipleaudio and video applications being used simultaneously in a vehicle. Forexample, the driver may listen to the radio, at the same time that apassenger in the backseat is engaging in a video conference. In suchsituations, the various sources of sound (and consequently noise) mayinterfere with each other, degrading voice quality of all applicationsinside the vehicle. Therefore, there is a need for performanceenhancement of audio by applying noise cancellation techniques tovehicle subsystems.

In a vehicle that does not offer combined networking capabilities forvarious possible networks, each of the devices associated with aparticular network (e.g., CAN bus sensors, mobile devices, GPS, etc.)may have a one-to-one mapping to either a human agent or to the vehicle.Network access is typically dictated by the human agent or vehiclemapped to the particular device. While some of these devices may be usedby other human agents (e.g., another human agent borrows a cell phone,has account privileges on a laptop, borrows an automobile with a GPS,etc.) network access does not ordinarily accommodate the preferences ofthe new user. In some cases, a mobile router used to facilitate networkaccess among various agents associated with a vehicle, could providepredetermined network access without regard to the particular agent ortransaction.

In a vehicle that provides networking capabilities between entitiesinside the vehicle and the external world (“connected vehicle”), theamount of possible transactions and the changeability of agentsassociated with those transactions require a flexible framework toensure appropriate network access. In a real-life scenario for aconnected vehicle, multiple agents may use the vehicle and performtransactions on or via the vehicle over any given time period.Individual users such as, for example, an owner, a driver, a passenger,a temporary driver (e.g., borrower or renter), or a new owner of a usedautomobile, may use the vehicle as a personal computing andcommunication platform for navigational, recreational, and/orbusiness-related purposes. A manufacturer of the vehicle may want tocollect vehicle centric data from the vehicle and send firmware/softwareupgrades to the vehicle. Government entities may want to identify andlocate the vehicle for law enforcement or government regulation (e.g.,emissions controls) purposes. Vehicle dealers may want to obtain sensordata and other vehicle diagnostic information for maintenance updatesand/or scheduling. Thus, a one-to-one exclusive mapping between an agent(e.g., a human or a device) and a connected vehicle does not exist.

In a contrasting example, a one-to-one mapping is typically providedbetween a mobile phone and a single user. In a mobile phone, credentialsthat bind the user and the device may be stored in a physical subscriberidentity module (SIM) or provisioning module. Thus, if the mobile deviceis subsequently operated by a new user (e.g., someone borrowing themobile phone), the credentials in the current SIM, associated with theoriginal user, will be used to access a cellular network and to bill forthe network access usage. Thus, the original user mapped to the mobilephone could be billed for any network usage fees incurred by the newuser. In some cases involving the same service provider, the mobilephone can be provisioned with the new user's credentials by physicallyreplacing the existing SIM hardware with a SIM of the new user. However,SIM swapping or identity reassignment across different service providersis often problematic or simply not feasible in a mobile phone.

In a connected vehicle, agents may change over any given period of time,and it may be impossible or impractical to physically switch a SIM inthe vehicle or to make a trip to a service center each time a new agentneeds network access to or from the vehicle. In one example, amanufacturer of an automobile may want to use a transaction applicationto collect real time data from sensors in the vehicle. If the automobileis manufactured in one country and shipped to another country (e.g.,manufactured in Japan and shipped to the United States), then before theautomobile is even purchased it would have traveled across internationalboundaries and multiple telecom service provider areas. Thus, if themanufacturer (i.e., the agent) provisions the automobile withcredentials for a first service provider usable in the first country,the manufacturer may prefer a different service provider to beprovisioned in the automobile once the automobile is shipped to anothercountry.

Another example of possible agent changes in a vehicle includes owners,drivers, renters, and passengers of a vehicle. When an automobile issold to a customer, the new owner needs access rights to varioustransactions (e.g., toll payments, gas and charging stations, Internetcommerce, personal vehicle settings, etc.) provided by the vehicle. Inaddition, the new owner may need wireless access to networks and devicesexternal to the vehicle using an appropriate service provider. Theseaccess rights may need to change each time the vehicle is driven by adifferent driver (e.g., another person in the owner's family, a currentrenter of a rental car, etc.). In addition, if the vehicle is soldagain, a new owner and associated drivers and passengers also needaccess rights and the previously existing access rights need to beremoved from the vehicle. Finally, multiple agents may want to accessthe vehicle concurrently, such as a driver and one or more passengers ofthe vehicle who desire access rights to at least some of the vehicletransactions. For example, a passenger may want to use an Internetcommerce transaction to download music or videos, or the passenger maywant to pay for transportation costs, such as toll expenses and/or gasand charging station expenses.

In a connected vehicle where OBU 30 hosts various applications (e.g.,multimedia, collaboration, social, transportation, enterprise, originalequipment manufacturer (OEM), dealers, consumer, navigation, publicsafety, and communications), one challenge is providing suitable userinterfaces so that driver distraction is minimized. Statistics show thateven a split second distraction such as typing short message service(SMS) text, dialing a phone, or watching a screen may cause fatalaccidents. Similarly, elderly and disabled people may not be able to usesome of the standard input-output interfaces available in a connectedvehicle. Various touch-less user inputs may be available in vehicles.For example, voice interface is used to input alphanumericalinformation. However, reliability of such voice to text technology canbe low, particularly for people with accents, due to various noisefactors and the need for extensive voice processing. Moreover, disabledpeople who are unable to speak cannot use the system. Therefore, thereis a need for user interfaces that aggregate multiple sources of input,for example, touch, gestures and voice, to provide a user interface thatis simple to operate and that can minimize distractions inside vehicles.In addition, it may be advantageous to associate such a user interfacewith a suitable identity profile that matches agents with their uniquegestures, touches, and commands. A system for real-time synthesis andperformance enhancement of audio/video data, and noise cancellation andgesture-based user interface in a vehicular environment, outlined byFIG. 1, can resolve many of these issues.

Note that in this Specification, references to various features (e.g.,elements, structures, modules, components, steps, operations,characteristics, etc.) included in “one embodiment”, “exampleembodiment”, “an embodiment”, “another embodiment”, “some embodiments”,“various embodiments”, “other embodiments”, “alternative embodiment”,and the like are intended to mean that any such features are included inone or more embodiments of the present disclosure, but may or may notnecessarily be combined in the same embodiments. Furthermore, the words“optimize,” “optimization,” and related terms are terms of art thatrefer to improvements in speed and/or efficiency of a specified outcomeand do not purport to indicate that a process for achieving thespecified outcome has achieved, or is capable of achieving, an “optimal”or perfectly speedy/perfectly efficient state.

Turning to the infrastructure of FIG. 1, end user 2 can be associatedwith a human agent (e.g., a driver or passenger). End user 2 mayinitiate communication in communication system 10 via some network, andsuch communication may be initiated through any suitable device,inclusive of an in-vehicle mobile device 18 a or 18 b, display 28, and anavigation system 17, which could be integrated with infotainment system15. Mobile devices, such as in-vehicle mobile devices 18 a-b, areinclusive of mobile phones, smart mobile phones (smartphones), e-bookreaders, tablets, iPads, personal digital assistants (PDAs), laptops orelectronic notebooks, portable navigation systems, multimedia gadgets(e.g., cameras, video and/or audio players, etc.), gaming systems, otherhandheld electronic devices, and any other device, component, element,or object capable of initiating voice, audio, video, media, or dataexchanges within communication system 10. Data, as used herein in thisspecification, refers to any type of numeric, voice, video, or scriptdata, or any type of source or object code, or any other suitableinformation in any appropriate format that may be communicated from onepoint to another in electronic devices and/or networks.

In-vehicle mobile devices 18 a-b, and mobile devices external to vehicle4, may communicate with OBU 30 of communication system 10 through anywireless or suitable wired link and may be configured as a personal areanetwork (PAN) or a wireless personal area network (WPAN) or any otherappropriate networking architecture or system that facilitatescommunications in a network environment. Wired and wirelesscommunication links may be inclusive of any electronic link such aswireless technologies (e.g., Bluetooth, Zigbee, IEEE 802.11x, WiFiDirect, 60 GHz, ultrawideband (UWB), etc.), a USB cable, an HDMI cable,etc. Connection between mobile devices and OBU 30 may be configuredbased on particular needs and logistics. In one example, an externalmobile device may be connected to OBU 30 through a USB cable or wirelessnetwork when, for example, the external mobile device is a diagnostictool used by a mechanic for servicing vehicle 4.

Networks 40 represent external networks, which can be a series of pointsor nodes of interconnected communication paths for receiving andtransmitting packets of information that propagate through communicationsystem 10. Networks 40 offer communicative interfaces between any of thecomponents of FIG. 1 and remote nodes and other electronic devices oftransaction systems 50, authorized entities 98, and other vehicles 59.In one embodiment, OBU 30 in vehicle 4 many communicate with othervehicles 59 over an ad hoc network. Such communication may befacilitated through corresponding OBUs in other vehicles 59. Networks 40could be any local area network (LAN), wireless local area network(WLAN), wide area network (WAN), wireless wide area network (WWAN),metropolitan area network (MAN), wireless metropolitan area network(WMAN), wireless single hop or multi-hop vehicle-to-vehicle network,virtual private network (VPN), Intranet, Extranet, or any otherappropriate architecture or system that facilitates communications in anetwork environment. Networks 40 may include any suitable communicationlink to OBU 30 such as wireless technologies (e.g., IEEE 802.11, 802.16,WiFi, WiMax, etc.), satellite, cellular technologies (e.g., 3G, 4G,etc.), etc., or any combination thereof. Networks 40 may also includeconfigurations capable of transmission control protocol/Internetprotocol (TCP/IP) communications, user datagram protocol/IP (UDP/IP), orany other suitable protocol, where appropriate and based on particularneeds.

Embodiments of OBU 30 may include one or more distinct interfaces,represented by network interfaces 26, to facilitate communication viathe various networks (including both internal and external networks)described herein. Such network interfaces 26 may be inclusive ofmultiple wireless interfaces (e.g., WiFi, WiMax, 3G, 4G, white space,802.11x, satellite, Bluetooth, near field communication (NFC), LTE,GSM/WCDMA/HSPA, CDMA1x/EVDO, DSRC, GPS, etc.). Other interfacesrepresented by network interfaces 26, may include physical ports (e.g.,Ethernet, USB, HDMI, etc.), interfaces for wired and wireless internalsubsystems, and the like. Similarly, each of the nodes of communicationsystem 10 can also include suitable interfaces for receiving,transmitting, and/or otherwise communicating data or information in anetwork environment.

OBU 30 and other associated or integrated components can include one ormore memory elements (e.g., memory element 24) for storing informationto be used in achieving operations associated with the wirelessinterface selection, seamless mobility, access control, and/orinformation flow control, as outlined herein. These devices may furtherkeep information in any suitable memory element (e.g., random accessmemory (RAM), read only memory (ROM), field programmable gate array(FPGA), erasable programmable read only memory (EPROM), electricallyerasable programmable ROM (EEPROM), etc.), software, hardware, or in anyother suitable component, device, element, or object where appropriateand based on particular needs. The information being tracked, sent,received, or stored in communication system 10 could be provided in anydatabase, register, table, cache, queue, control list, or storagestructure, based on particular needs and implementations, all of whichcould be referenced in any suitable timeframe. Any of the memory orstorage options discussed herein should be construed as beingencompassed within the broad term ‘memory element’ as used herein inthis Specification.

In example embodiments, the operations as outlined herein may beimplemented by logic encoded in one or more tangible media, which may beinclusive of non-transitory media (e.g., embedded logic provided in anASIC, digital signal processor (DSP) instructions, software potentiallyinclusive of object code and source code to be executed by a processoror other similar machine, etc.). In some of these instances, one or morememory elements (e.g., memory element 24) can store data used for theoperations described herein. This includes the memory elements beingable to store software, logic, code, or processor instructions that areexecuted to carry out the activities described in this Specification.

Additionally, OBU 30 and associated or integrated components may includeprocessing elements 21 (e.g., computing processor 22, routing processor23, etc.) that can execute software or algorithms to perform activitiesto enable real-time synthesis and performance enhancement of audio/videodata, noise cancellation, and gesture based user interfaces, and toroute packets using suitable routing protocols. A processor can executeany type of instructions associated with the data to achieve theoperations detailed herein in this Specification. In one example, theprocessors (as shown in various FIGURES) could transform an element oran article (e.g., data) from one state or thing to another state orthing. In another example, the activities outlined herein may beimplemented with fixed logic or programmable logic (e.g.,software/computer instructions executed by a processor) and the elementsidentified herein could be some type of a programmable processor,programmable digital logic (e.g., an FPGA, an EPROM, an EEPROM), or anASIC that includes digital logic, software, code, electronicinstructions, flash memory, optical disks, CD-ROMs, DVD ROMs, magneticor optical cards, other types of machine-readable mediums suitable forstoring electronic instructions, or any suitable combination thereof.Any of the potential processing elements, modules, microprocessors,digital signal processors (DSPs), and other devices described in thisSpecification should be construed as being encompassed within the broadterm ‘processor.’ Regarding a physical implementation of OBU 30 and itsassociated components, any suitable permutation may be applied based onparticular needs and requirements, including the design of theparticular vehicle in which OBU 30 is implemented.

In example implementations, various components of OBU 30 may beinstalled in different physical areas of the vehicle or may be installedas single unit, with display 28 being positioned to allow driver access.Other displays may be provided in suitable locations for access bypassengers in particular passenger seats. In one implementation,multimedia, networking, and communication components may be positionedat some distance from the vehicle engine (e.g., in or near the rear ortrunk area if the engine is in the front area of the vehicle).

Communication system 10 may be configured to facilitate communicationwith machine devices (e.g., vehicle sensors, instruments, electroniccontrol units (ECUs), embedded devices, actuators, etc.). OBU 30 may beimplemented to provide one or more suitable communication interfaces(e.g., network interfaces 26) to legacy systems in vehicles such as, forexample, a controller area network (CAN) a low speed network (LIN), aflexray communications protocol network, media oriented systemstransport (MOST), and the like. Typically, multiple ECUs, with differentembedded software, may be found in a single automobile and maycommunicate via a CAN bus. Sensors 14 a-b may represent, for example,wheel and headlight sensors, respectively. Controls 16 a-b may beinclusive of any embedded system or ECU that controls one or more of theelectrical systems or subsystems in vehicle 4. Actuator 13 represents avehicle-setting device such as, for example, a seat positioning devicefor adjusting various seat positions (e.g., longitudinal positionrelative to the brake and gas pedals, tilt position, lumbar support,etc.). Actuator 13 and other similar vehicle setting devices (e.g.,temperature controls, sunroof, door locks, power windows, etc.) may beconfigured for communications in a LIN bus, in one embodiment. Sensor 14c represents a type of sensor or device that may be configured forcommunications via flexray communications protocol (e.g., a radarcollision sensor). Control 16 c, representing one or more ECUs, may besuitably integrated for controlling the flexray network and sensors andother associated components. Additionally, OBU 30 may be implemented toprovide one or more suitable communication interfaces (e.g., networkinterfaces 26) to an Internet Protocol (IP) network, user datagramprotocol (UDP) network, or any other suitable protocol or communicationarchitecture provided to enable network communication with machinedevices in vehicle 4.

In this particular example, vehicle 4 includes capabilities associatedwith navigation system 17 and vehicle diagnostics 19. Navigation system17 may be provided in various embodiments including, for example, aportable navigation system or, alternatively, a fixed navigation system,each of which may be configured for wireless or wired communications toOBU 30. Other more specific machine devices, not shown in FIG. 1, mayinclude display panel instruments, climate controls, interior lights,door locks, trunk open/shut actuator, hood open/shut actuator, seatheater and/or cooler, sunroof open/shut actuator, windowheater/defroster/defogger, entertainment systems (e.g., speakers, radio,DVD, CD, etc.), and the like.

Turning to FIG. 2, communication system 10 is illustrated with OBU 30shown coupled to agents 90 and networks 40. As previously discussedherein, agents 90 can include machine devices 92, humans 94, and mobiledevices 96. In addition, agents can also include software agents 95 andauthorized entities 98. Software agents 95 can include any applicationor executable file comprising instructions that can be understood andprocessed on a computer, and provisioned in a memory element accessibleto OBU 30 (e.g., memory element 24), and which may be initiatedautomatically in response to a particular set of criteria or conditions(e.g., every time network connectivity is detected on OBU 30, wheneverOBU 30 is powered on and a particular time interval has passed, inresponse to another software agent, etc.).

Authorized entities 98 may include various entities having authorizationto access a vehicle 4 such as, for example, a dealer of the vehicle, amanufacturer of the vehicle, OEMs associated with the vehicle, andpublic entities having an interest in the vehicle (e.g., StateDepartments of Transportation, local police departments, etc.). A nodeof such authorized entities will typically be remotely located from OBU30 and, therefore, accessible from OBU 30 through networks 40 such asthe Internet or other WANs and any available communication link (e.g.,3G, 4G, WiFi, WiMax, etc.) providing network access from OBU 30 to theInternet or other WAN. In some scenarios, however, OBU 30 may be locallyaccessible to an authorized entity such that Internet access isunnecessary. For example, when vehicle 4 is being manufactured and islocated at one of the manufacturer's facilities, OBU 30 may be capableof accessing the manufacturer's network through a LAN or WLAN.Similarly, when a vehicle 4 is taken to a dealer for maintenance, theOBU 30 may connect to the dealer network through a communication linkthat does not include the Internet or any other wide area network.

Networks 40 may also facilitate communication between certain agents 90(e.g., machine devices 92, humans 94, software agents 95, mobile devices96) and transaction systems 50. By way of example, transaction systems50 may include services transaction systems 52, commercial transactionsystems 54, road-side transaction systems 56, end user transactionsystems 57, and transportation transaction systems 58 on nodes or otherelectronic devices. Each of the transaction systems can be associatedwith many different types of entities and many different transactionscenarios. Services transaction systems 52 can encompass numerousentities providing services such as identity service providers, mobilewireless service providers, banks and other financial institutions,location-based services (LBS), travel agencies, vehicle rental andleasing agencies, Internet websites, etc. Commercial transaction systems54 may include entities facilitating commercial transactions through theInternet (e.g., video and music download sites, online retailers, etc.),etc. Roadside transaction systems 56 may include various entitiesproviding roadside services such as gas and electric charging stations,kiosks (both roadside and drive-through), etc. End user transactionsystems 57 may include end user devices (e.g., mobile devices, laptops,personal computers, cellular telephones, etc.) for communication withOBU 30 through networks 40.

Transportation transaction systems 58 may include entities or devicesfacilitating vehicle charging transactions related to toll payments,ferry charges, bridge toll payments, parking, Vehicle Miles Traveled(VMT), and any other transportation costs incurred as a result of movingvehicle 4 from one location to another. All of the transaction systems50 (e.g., transaction systems 52, 54, 56, 57, 58) as categorized, areprovided for purposes of illustration and ease of understanding, and itwill be appreciated that certain entities may logically be included inmultiple transaction systems (e.g., a bank could be described as both aservices transaction system and a commercial transaction system) andthat numerous types of transaction systems and entities other than thoseenumerated herein may also be possible.

Other commercial transactions may occur through OBU 30 by accessingother vehicles 59 (vehicle-to-vehicle commerce). An available networkrepresented by networks 40, may provide a communicative pathway betweenvehicle 4 and other vehicles 59, where vehicle 4 includes OBU 30 andother vehicles 59 include a suitable communication device (e.g., mobiledevice, OBU or similar device). The communicative pathway (i.e., path)between vehicle 4 and other vehicles 59 could be established as a singlehop or multi-hop vehicle-to-vehicle network through WiFi, WiMax, or anyother suitable wireless technologies allowing a sustained connectionbetween vehicle 4 and other vehicles 59.

Commercial transactions could occur between a mobile device in onevehicle (connected to an OBU) and an OBU in another vehicle, betweenmobile devices in separate vehicles with OBUs, or between OBUs ofseparate vehicles. Commercial transactions may also be conducted betweenOBU 30 and mobile devices 96 (vehicle-to-mobile device commerce), suchas when a mobile device purchases content from OBU 30 of the samevehicle. Another type of commercial transaction can include in-vehiclecommerce in which a user of a mobile device pays for the use ofresources through OBU 30 (e.g., in the case of a passenger in acommercial vehicle such as a taxi cab) or when mobile devices within avehicle use the network available through OBU 30 to conduct commercialtransactions with each other. In addition to commercial transactions,these communicative pathways involving vehicles and mobile devices mayalso be established for any other suitable services or transactions,providing proper authentication and network credentials are obtained.

Applications installed on OBU 30 can be considered transactionapplications and can include a plethora of user-level and system-levelapplications. With proper authentication to OBU 30 and authorization,numerous types of transactions using the transaction applications may beperformed through OBU 30. Generally, types of transactions are inclusiveof 1) accessing one or more wireless/mobile/cellular networks and usingnetwork bandwidth and services, 2) gaining access to various resourcesof the vehicle, 3) gaining access to applications in the vehicle, and 4)engaging in commercial activities (e.g., paying for receiving goods orservices, or receiving payment for selling goods or services).

Turning to FIG. 3, FIG. 3 illustrates a simplified block diagram of acommunication system 10 according to embodiments of the presentdisclosure. Communication system 10 may leverage OBU 30 andinter-vehicle routing protocols to supplement cloud data (i.e., datalocated via Internet, Enterprise and other clouds) with live, local andtransient data collected from other vehicles and nearby locations. Theability to communicate directly with peers can also create opportunitiesfor sharing and storing localized geosocial information in vehicularclouds and/or local roadside infrastructure devices. Given thepotentially large amount of cloud and local data, OBU 30 can prioritizethis information, possibly taking into account a user's preferences, andmay express the information to the user via suitable user interfaces.

Disparate sources of information may be filtered through OBU 30 andpresented to users (e.g., user 2) in appropriate formats, possibly basedon user preferences and pre-specified priority levels. For example,emergency alert data (ambulance, police, accident prevention, etc.) maybe categorized as high priority information and preempt other data.These alerts may be largely event triggered (e.g., upon detecting anambulance coming towards the vehicle). Further, priority levels are alsopossible with collision avoidance, for example, being a higher prioritythan other events. Other user and sensor-generated alerts related tonon-critical aspects, for example, a vehicle condition, may take a lowerpriority after emergency alerts. Such alerts may include informationabout broken taillights, potholes, accidents, etc.

Presentation of alerts can be customized for each user. For a majorityof users, auditory signals with different levels of urgency may beappropriate. For other users, visual cues or haptic feedback may be moreappropriate. Further, OBU 30 can minimize driver distraction bysuppressing, if needed, any other forms of data display during emergencyalerts.

Aside from emergency and vehicle alert data, a user may actively searchcontent or may have content pushed to OBU 30. Relevancy of such data maybe assessed based on various factors, including user preferences,proximity, timeliness, and/or relevance to other users seeking the sameinformation in the same geographical neighborhood. OBU 30 may filter allincoming data and present such information to users in the vehicle basedon user-specified interface formats.

In FIG. 3, various geo-social information sources such as remote nodes202, for example, emergency vehicles, other vehicles, roadsideinfrastructure devices, Internet, etc., may send a data packetcontaining information to OBU 30. For example, an emergency vehicle maysend traffic alerts to OBU 30 with information regarding its locationand speed. The data packet containing the alert data may also containinformation regarding the data packet size, format, and origin anddestination addresses.

Similarly, various agents 90, such as machine devices, and softwareagents, may also be information sources, sending data containinginformation to OBU 30. For example, a sensor in the vehicle may send analert to OBU 30 when tire pressure is low. Additionally, remote nodesmay send data containing information to OBU. For example, a mobiledevice operating externally to vehicle 4 (e.g., a mobile device inanother vehicle traveling behind vehicle 4) may send data informing OBU30 of broken brake lights. In one embodiment, remote nodes 202 may beexternal to the vehicle, and agents 90 may be in-vehicle devices. Datareceived from multiple sources, for example, remote nodes 202 andin-vehicle agents 90, may compete for resources on OBU 30. Data receivedfrom such sources may be presented to a user 2 in a manner conveying anappropriate level of importance or criticality assigned to the message,while minimizing distraction to the user.

OBU 30 can include various control modules and data processing modulesincluding a user preference database module 204 to process theinformation contained in the data. User preference database module 204may provide configurability and customizability to a user regardingvarious user preferences, for example preferences regarding a data type,a data format and a medium through which the user receives the data. Asused herein, ‘medium’ encompasses channels and tools used to deliverdata, including by electronic and physical means, for example, videodisplays, speakers, and mechanical vibrators. User preference databasemodule 204 may provide an interface to the user through which the usercan set the various user preferences. User preference database module204 can also allow the user to determine a medium through which the userlikes to receive different types of data, for example, through audio ormechanical, such as alerts through steering wheel vibrations. Apart fromsetting static preferences, user preference database module 204 can alsoallow the user to change the various user preferences dynamically. Forexample, if the user wants to find advertisements for a shoe sale in aparticular locality, the user can set a preference that may be used by apriority mapper module 206 to increase the importance of any relevantdata related to shoe sales in the particular locality.

Priority mapper module 206 can create a mapping from the received datatypes to priority levels associated with the data types based on thevarious user preferences stored in user preference database module 204.In one embodiment, the priority level of a data type indicates thepriority to be given to data associated with that data type whenprocessing multiple data. Priority mapper module 206 may use a defaultpriority map from a default priority mapper module 208 as a referenceand modify any preset priorities in default priority mapper module 208using the user preferences from user preference database module 204.Default priority mapper module 208 may store a preset mapping ofdifferent data types with corresponding priority levels. For example,traffic alerts may be set to a priority of 1, 1 being the highestpriority, and advertisements may be set to a priority of 10, 10 beingthe lowest priority. In some cases, priority mapper module 206 may notchange default priority levels set by default priority mapper module208. For example, the user may not be able to change a priority levelassigned to entertainment information over a relative priority levelassigned to safety alerts.

The priority mapping information from priority mapper module 206 may besent to a data parser and classifier module 210. Data parser andclassifier module 210 can receive raw data from geosocial informationsources, can process the data, and can extract certain information usingpredefined rules. For example, different sources may produce the sameinformation in different formats, such as text and audio. Data parserand classifier module 210 can convert the various formats in which thedata is received to a standard format usable by the various controlmodules and data processing modules of OBU 30. Data parser andclassifier module 210 may determine data formats based on various rules,for example, data arriving at a specific port may be assigned a specificformat, and data from a particular application may be assigned adifferent format.

Data parser and classifier module 210 can tag the information with asuitable priority level using a priority mapping created by prioritymapper module 206. Tagged data from data parser and classifier module210 may be sent to a priority filter module 212, which can read prioritytags on the data and place the data into different priority queues. Thepriority queues can, for example, be numbered 1 through 10, 1 referringto the data containing the most important information such as safetyalerts; and 10 referring to the data containing the least importantinformation such as advertisements. Priority filter module 212 can alsoreorder data within the queues to ensure temporal integrity of the data(e.g., data within each queue is ordered based on the time of itsgeneration).

When priority filter module 212 receives data containing informationthat may not be immediately relevant or presented to the user, priorityfilter module 212 may store the data in a data store module 214. Forexample, priority filter module 212 may receive unimportantadvertisement information at the same time that it receives an importanttraffic alert. It may be dangerous to present the advertisement to theuser before the traffic alert. Therefore, priority filter module 212 maystore the data containing advertisement information in data store module214, while presenting the traffic alert information to the user. Inanother embodiment, priority filter module 212 may receive an importanttraffic alert that may have higher priority than the stored data in thepriority queue. Therefore, priority filter module 212 may move a lowerpriority data from the priority queue to the data store module 214 andplace the higher priority traffic alert in the priority queue.Additionally, data store module 214 may help alleviate congestion of apotentially large volume of information generated by the informationsources and received by the OBU.

In another example, priority filter module 212 may store data containinginformation that is not immediately needed by the user, but which may beimportant in the future, such as information about rain 20 miles aheadon a freeway. In that case, priority filter module 212 may put the datacontaining the information about rain in data store module 214 insteadof in the priority queues. When the information about rain becomesrelevant, data store module 214 can insert the data containing theinformation about rain back into the priority queues for furtherprocessing. Data store module 214 can also serve as a repository fordata, wherein all or part of the data received by the data store module214 can be stored permanently for later reference based on userinstructions.

In the embodiment according to FIG. 3, it is possible that OBU 30 mayreceive the same information from multiple information sources, due tothe wide variety and large number of potential information sources. Forexample, an emergency vehicle in upstream traffic may cause vehicles tenblocks ahead to slow down. Cars proximate the emergency vehicle may senda traffic alert about the emergency vehicle to OBU 30. Meanwhile, speedsensors in a vehicle five blocks ahead may detect traffic congestioncaused by the emergency vehicle and relay the traffic congestioninformation to OBU 30. When information from both these sources isreceived by OBU 30, priority filter module 212 may assign differentpriorities to the traffic alert and the traffic congestion information.For example, the traffic alert may receive a higher priority than thecongestion information. Nevertheless, both the traffic alert and thetraffic congestion information indicate the same event. In such case, adata combiner/fuser module 216 may enable only one of the information inthe multiple data to be displayed to the user. Data combiner/fusermodule 216 can analyze information in the data in the priority queuebased on related information types and can estimate whether theinformation is indicative of the same event. Data combiner/fuser module216 may either delete the redundant information, or combine theinformation to produce an alert with more information.

Each type of information in the data can be presented to the user inmultiple ways. For example, a traffic alert can be shown on a windshieldheads-up display (HUD) or a front display, or played out on an audiosystem. Information requested by a backseat passenger may be shown on abackseat display or provided through a backseat audio system. Apresentation media selector module 218 can determine the best method topresent the available information. In one embodiment, the determinationmay be based on predefined algorithms that can be tuned by userpreferences. For example, a user may prefer to get all messages over theaudio system while another user may prefer to get the information viathe HUD. In another example, the priority level may determine thepresentation. Thus, a high priority traffic alert may be presented viasteering vibration, and a low priority advertisement may be playedsimultaneously on the audio at low volume.

Even after a presentation medium is selected, there may be a need toswitch the medium dynamically. For example, an advertisement may beplayed over the audio system when there are no other competing alerts orsounds presented to the user. However, if a high priority traffic alertis received at the same time that the advertisement is being played out,the traffic alert may be prioritized over the advertisement and can beplayed out over the audio system.

A presentation media controller module 220 can handle multiple streamsof data containing information with differing priorities simultaneously,and can seamlessly transfer the data to a suitable medium, temporarilydelay the presentation of the data, end the presentation of the data, orperform any suitable combination thereof. In the example describedabove, the data containing advertisement information could betransferred to a front display, and the data containing traffic alertinformation could be transferred to a steering vibrator. Media drivermodules 222 a-c may be coupled to OBU 30 and can directly control eachpresentation medium to convert information received into a format forpresentation by the corresponding medium. For example, media driver 222a controls windshield HUD, and can convert a traffic alert informationinto a format accessible by the windshield HUD. Media driver 222 b onthe other hand, may convert the same traffic alert information into adifferent format that is accessible by speakers. Media driver 222 c mayconvert the same traffic alert information into yet another formataccessible by a rear seat display.

Thus, according to various embodiments of the present disclosure, thevarious control modules and data processing modules in OBU 30 may causeimproved emergency response. For example, emergency responders (e.g.,ambulances, fire trucks, and police units) can broadcast an emergencysignal that contains the live GPS location of the emergency responder aswell as routing information from the emergency responder's navigationsystem. This information can propagate through multiple OBUs in trafficas each vehicle receives it and rebroadcasts it to other nearbyvehicles. Thus, for each driver in the affected area (e.g., geographiclocations close to the emergency responder), a live display of theemergency responder's location may appear on the respective vehicle'sGPS system. In addition, if vehicle navigation systems are active (forexample, if map and routing information can be updated in real time),the navigation systems may automatically reroute a vehicle, or multiplevehicles, out of a path of the emergency responder. Moreover, suchinformation could enable drivers of the vehicles to adjust their drivingbehavior to better accommodate the emergency responder.

Embodiments according to FIG. 3 may also cause reduced trafficcongestion. For example, a vehicle may be travelling abnormally slowly(for example, moving at 10 mph on a freeway with a speed limit of 70mph). Such slow moving traffic information can be broadcasted by nearbyvehicle OBUs and propagated through traffic. Vehicles heading into suchcongestion may receive this information and the vehicles' respectivenavigation systems may automatically reroute the vehicles around thecongestion, resulting in traffic easing up around the slow movingvehicles as downstream traffic is rerouted.

In yet another example embodiment, more efficient use of time and spacemay be achieved. For example, a downtown parking lot or garage in acrowded city may experience congestion caused by vehicles searching foran open parking space. A parking lot or garage computer may sense thecongestion and broadcast open space information to vehicle OBUs. Forexample, the computer may cause the driver to be alerted that theparking lot is full, and provide information about a location of thenearest alternative parking lot. An example embodiment according to FIG.3 may also affect information relay between vehicles in motion. Forexample, a user may send a maintenance alert via OBUs to the driver of avehicle ahead, of broken brake lights, without needing a phone number orother identity information.

The embodiment according to FIG. 3 may support location awareadvertising. For example, OBUs may be able to communicate withrestaurant computers (e.g., location-specific information broadcast fromthe restaurant) in a nearby locality and determine restaurant specials,deals, and queues. Other systems in the vehicle can piggyback on thetransient network created and maintained by OBU 30 to provide moreentertaining experiences for the passengers in the vehicle. For example,a handheld video game console can provide social interactions or gameplay between players in different vehicles, without having to implementthe handheld video game console's own protocols or use high poweredcommunications radios. The handheld video game may rely on OBUs insidethe vehicles to maintain network connectivity among the vehicles (e.g.,an ad hoc network) and provide a communications medium. Similarly, avariety of other applications may use the OBU's network as a platformfor providing an enhanced entertainment experience inside the vehicle.

Thus, OBU 30 can create a local network between nearby vehicles. Thelocal network enables an applications layer that can be used by variousapplications to enhance user experience inside the vehicle. A largeamount of highly transient, locally specific information may be easilyand efficiently accessed by drivers without resorting to a store/fetchmodel of a cloud based network. Such access to highly transient, locallyspecific information may be enabled by mesh networks created anddestroyed dynamically by OBU 30 and sensory data captured from vehiclesand vehicle occupants. OBU 30 may act as a synthesizer, combininglarge-scale information from the cloud (like directions and point ofinterest (POI) searches) with locally acquired information, andselectively filtering the information to provide the most relevant datato the driver in a prioritized and minimally distracting fashion, as maybe determined by the importance and criticality of the information.

Turning to FIG. 4, FIG. 4 is a flow-chart illustrating exampleoperational steps of a method 240 for real time synthesis of dataaccording to an embodiment of the present disclosure. The method startsin step 242. In step 244, remote nodes 202 and/or agents 90 send data toOBU 30. Various user preferences about data formats, priority, and othercriteria can be stored in user preference database module 204 in step246. Default priority maps can be created and stored in default prioritymapper module 208 in step 248. Priority mapper module 206 may createpriority levels for various data based on default priority maps and userpreferences in step 250. In one embodiment, if user 2 does not setpreferences for priority levels, priority mapper module 206 may assignpriority levels based on default priority maps from default prioritymapper module 208. In another embodiment, user preferences from userpreference database module 204 may be used to set priority levels bypriority mapper module 206.

Data parser and classifier module 210 tags the data from remote nodes202 and/or agents 90 with priority levels from priority mapper module206 in step 252. Priority filter module 212 places the data in priorityqueues in step 254. In step 256, priority filter module 212 makes adecision to present the data to the user. In example embodiments, thedecision may be based on information contained in the data, userpreferences, proximity, timeliness, and/or relevance to other usersseeking the same information in the same geographical neighborhood,priority level and other considerations. If the data is not presented tothe user as determined in step 256, the data is stored in data storemodule 214 in step 258. The data in data store module 214 may beperiodically checked to determine whether it may be presented to theuser.

If the data may be presented to the user, data/combiner fuser module 216determines whether the data in the priority queue contains redundant orduplicate information in step 260. If the data in the priority queuecontains redundant information, data combiner/fuser module 216 combinesredundant information or eliminates duplicate information in step 262.Data is sent to presentation media selector module 218 that selects apresentation medium in step 264. Presentation media controller module220 converts the data to a media format in step 266 and the data ispresented to the user via the selected media in step 268. The methodterminates in step 272. Thus, OBU 30 can present data containing diverseinformation from multiple sources to the driver in a minimallydistracting and preferred way.

Turning to FIG. 5, FIG. 5 is a simplified schematic diagram of anexemplary communication system 10 for performance enhancement of Voiceover IP (VoIP) and video streams in accordance with embodiments of thepresent disclosure. In one example network session, OBU 30 in vehicle 4may be in communication with end nodes operating within vehicle 4 andexternally to vehicle 4, in addition to other possible intermediateremote nodes. In the example shown in FIG. 5, one end node may includean in-vehicle device 280 and another end node may include correspondingend node 282. The network session may be established through one or moreremote nodes such as a network controller 284. OBU 30 may connect to theInternet via multiple wireless interfaces (e.g., 3G, WiFi, WiMax) whileproviding various voice and video services to in-vehicle device 280(e.g., built-in music and movie players, laptops, smart phones, etc.).In accordance with embodiments disclosed herein, network controller 284can perform various network functions, including ID/location mapping,shaping, proxy, etc. Furthermore network controller 284 can beimplemented in a centralized or distributed manner in a network cloud.

OBU 30 may be in communication with in-vehicle device 280 via link 296a, which may be wired or wireless. Examples of wired links includeEthernet, Controller Area Network (CAN) buses, Local Internet Network(LIN) buses, and Media Oriented System Transport (MOST) buses. Examplesof wireless links include IEEE 802.11, 802.16, WiFi, Bluetooth, andWiMax. Network controller 284 may be in communication with remote node282 via link 296 b, which may be a wireless link such as WiMax, 3G, or4G. OBU 30 and network controller 284 may communicate with each othervia multiple wireless links 298, including WiFi, WiMax, 3G, 4G, 802.11x,satellite, Bluetooth, near field communication (NFC), LTE,GSM/WCDMA/HSPA, CDMA1x/EVDO, DSRC, GPS, etc. Each link may traverse adistinct path. For example, data packets on a WiFi link may be sentdirectly from OBU 30 to a wireless access point and then to networkcontroller 284. On the other hand, data packets on a 3G link may betransmitted via satellite to network controller 284.

Each of OBU 30 and controller 284 are coupled to a path/link statemonitor 286 a-b, video/voice encoder 288 a-b, video/voice packet metainformation extractor 290 a-b, and performance enhancer 292 a-b, one ormore of which may be used, alone or in combination, for performanceenhancement of incoming voice and video traffic. Each of OBU 30 andcontroller 284 may also be equipped with multiple network interfaces 26a-b such as network interfaces 1, 2 to n corresponding to multiplewireless links (and/or paths) 298. Each of OBU 30 and controller 284 mayalso be coupled to a storage device, for example, data store 294 a-bthat is adapted to store information such as link quality and pathstatistics.

By way of example for illustrating an operation of communication system10, in-vehicle device 280 in vehicle 4 may be a phone transmitting voiceto corresponding end node 282, which may be another phone. One or moreof multiple wireless links 298 may experience poor link quality duringthe voice transmission as the vehicle moves. For example, a WiFi linkmay experience poor link quality relative to 3G and GSM/WCDMA/HSPAlinks. Therefore, OBU 30 may use one or more of path/link state monitor286 a, video/voice encoder 288 a, video/voice packet meta informationextractor 290 a, and performance enhancer 292 a to transmit the voicevia wireless links that experience better link quality, for example 3Gand GSM/WCDMA/HSPA. However, selecting links with the best link qualitymay be difficult when sending the same information across multipleinterfaces with potentially completely different paths.

It will be appreciated that although the example has been describedabove in a situation where OBU 30 receives the voice traffic fromin-vehicle device 280, the method is applicable to situations wherenetwork controller 284 receives voice traffic from corresponding endnode 282. Controller 284 may use one or more of path/link state monitor286 b, video/voice encoder 288 b, video/voice packet meta informationextractor 290 b, and performance enhancer 292 b to enhance the voicetraffic to OBU 30 despite poor link quality on one or more wirelesslinks 298.

Turning to FIG. 6, FIG. 6 is a simplified block diagram illustrating acommunication system 10 for performance enhancement of VoIP and videostreams, according to embodiments of the present disclosure. Video/voiceencoder 288 may convert incoming raw video/voice stream 302 intocompressed and encoded media packets 304. As used herein, the term‘voice’ encompasses all types of audio, including speech, noise, ambientsound, nature sounds, musical instruments (with or without vocals),etc.). In an example embodiment, video/voice encoder 288 may reside onan end node, for example a phone inside a vehicle. In another exampleembodiment, video/voice encoder 288 may reside on OBU 30. For example,if a vehicle is equipped with a video conferencing system, video/voiceencoder 288 may be embedded in OBU 30 inside the vehicle. Video/voiceencoder 288 may compress video/voice stream 302 to reduce a number ofbits used to represent a video/voice sequence in video/voice stream 302,for example, by exploiting both temporal and spatial redundancy.Video/voice encoder 288 may also minimize any losses on decoded videoquality, for example, by encoding the video/voice sequence invideo/voice stream 302 in an error resilient way.

Compressed and encoded media packets 304 may be sent to video/voicepacket meta information extractor 290 and performance enhancer 292. Metainformation extractor 290 generates meta information 306 aboutcompressed and encoded video/voice packets 304. Meta information 306 mayinclude bit depth, packet size, priority, distortion contribution, anddecoding deadline. Meta information 306 may be sent to the performanceenhancer 292.

Path/link state monitor 288 can obtain path/link statistics 308 fromdynamic online measurements 310 of various path and link characteristicsof links 298, such as round trip time (RTT) over each path, availablebandwidth over each path and packet loss ratio over each wireless linkfrom various interfaces 26 (referred to individually and collectivelyherein as interface 26 or interfaces 26, respectively), for exampleinterfaces 1, 2, . . . n. Path/link statistics 308 may be updatedperiodically to track time-varying conditions of wireless links (and/orpaths) 298. Path/link state monitor 286 can feed path/link statistics308 to performance enhancer 292. Performance enhancer 292 may usepath/link statistics 308 and meta information 306 to perform variousoptimization procedures on compressed and encoded video packets 304 tocreate enhanced media streams 312 (referred to individually andcollectively herein as media stream 312 or media streams 312,respectively) including: 1) optimal media-aware rate calculation; 2)retransmission limit selection for each media packet; 3) channel codingfor error protection across multiple links (and/or paths); and 4)optimal path assignment for individual media packets. Performanceenhancer 292 may transmit enhanced media streams 312 across one or moreinterfaces 26.

Turning to FIG. 7, FIG. 7 illustrates a flow-chart with exampleoperational steps for a method 330 associated with performanceenhancement of voice and video streams according to embodiments of thepresent disclosure. Voice/video stream 302 is incoming in step 332. Metainformation 306 is extracted from stream 302 by meta informationextractor 290 in step 334. Connectivity of transmission interfaces 26 iscalculated and/or predicted by performance enhancer 292 in step 336.Performance enhancer 292 can generate media streams 312 for multiplelinks (and/or paths) 298 in step 338. Generating multiple media streams312 may be based at least on matching data transfer rate of each mediastream 312 to available bandwidth across the corresponding interface. Inan example embodiment, streaming media quality, for example, voicequality of VoIP calls, and resolution and frame rate of streamed videocontents may be matched to available overall throughput (e.g.,bandwidth) of wireless links 298 before transmitting the data. Inanother example embodiment, total available bandwidth of wireless links298 may be allocated across multiple media streams 312 based on mediacharacteristics of individual media streams 312 to enhance userexperience.

Alternatively, performance enhancer 292 may generate a channel-codedstream in step 340. Channel coding may enable media streams 312 to betransmitted and received with minimal errors. In one example embodiment,coded (e.g., redundant) bits may be added to generate the channel codedstream. In another example embodiment, block codes may be added togenerate the channel-coded stream (e.g., redundant bits may be added toone end of a block of data). Performance enhancer 292 may disperse thechannel-coded stream into media streams 312 across multiple interfacesin step 342 based at least on matching data transfer rate of each mediastream 312 to available bandwidth across the corresponding interface. Inan example embodiment, media packets and coded error protection packetsmay be dispersed over multiple links (and/or paths) to achieve morerobust error protection. In another example embodiment, error protectionlevels of different media streams 312 may be differentiated based on arelative importance of each media packet in the media stream 312 and awireless channel condition of a link 298 over which media streams 312are transmitted. Media streams 312 are transmitted across multipleinterfaces 26 in step 344.

Turning to FIG. 8, FIG. 8 is a flow-chart illustrating exampleoperational steps for a method 350 associated with calculating and/orpredicting connectivity of an interface. Method 350 starts in step 352.Loss rate of each interface 26 is measured by path/link state monitor286 in step 354 and the loss rate is stored in data store 294 in step356. Received signal strength indication (RSSI) on each interface 26 ismeasured by path/link state monitor 286 in step 358 and stored in datastore 294 in step 360. RSSI measurement on interface 26 may indicate apower in a signal on interface 26. If the RSSI measurement of interface26 is below a certain threshold, a packet of information can be sent oninterface 26. RSSI measurements may also be used in statistical analysisto determine connectivity empirically. In step 362, link quality ismeasured by path/link state monitor 286 on each interface 26 usingwell-known formulae, for example, as a ratio of arrived packets toexpected packets. Threshold values of RSSI, RSSI measurements,statistical parameters and loss rate measurements may be extracted byperformance enhancer 292 from data store 294 in step 364. In step 366,connectivity can be predicted by performance enhancer 292 based on linkquality and information extracted from data store 294. The method endsin step 368.

Turning to FIG. 9, FIG. 9 is a flow-chart illustrating exampleoperational steps that may be associated with a method 370 fordynamically matching overall stream source rate with total availablebandwidth over multiple wireless links according to an embodiment of thepresent disclosure. Using one or more optimization procedures, OBU 30may adaptively change a data transfer rate of encoded video packets 304based on network conditions and corresponding interfaces, andperformance requirements of VoIP and video stream 302. Method 370 mayadapt the data transfer rate of media stream 312 on each link 298 basedat least on an available bandwidth across a corresponding interface.Thus, for multiple media streams 312 competing for limited bandwidthacross multiple links 298, data transfer rate calculation according toan example embodiment may allocate different data transfer rates fordifferent media streams 312 dynamically. In addition, a streaming mediaquality (e.g., voice quality of VoIP calls, resolution and frame rate ofstreamed video contents) may be matched to available overall throughput(e.g., bandwidth) of wireless links 298.

In FIG. 9, voice/video stream 302 is incoming in step 372. Metainformation 306 is extracted from voice/video stream 302 in step 374.Connectivity of transmission interfaces 26 is calculated and/orpredicted by performance enhancer 292 in step 376. Traffic ratedistributed over each path may be monitored by path/link state monitor286 to determine whether a bandwidth limit of the path is being exceededby measuring bandwidth across each interface 26 in step 378 andmeasuring traffic rate on each available link in step 380. Bandwidthacross each interface 26 may be measured by various techniques (e.g., byonline end-to-end bandwidth measurement for each link, using alightweight packet probing method of periodically transmitting a trainof packets, etc.) to estimate the available bandwidth over a given path.

Performance enhancer 292 may calculate a data transfer rate across eachinterface by matching data transfer rate to available bandwidth acrossthe interface in step 382 by rate adaptation techniques, for example,stream source rate adaptation. Data transfer rate matching to availablebandwidth may also ensure that total available bandwidth is matched withan overall data transfer rate for all media streams 312. For example,transcoding, scalable encoding, packet pruning, or bitstream switchingmay be applied to media streams 312 to dynamically tune each mediastream's data transfer rate and corresponding quality. For audio,enhancement-layer packets may be dropped from an incoming scalablevoice/video stream 302. In an example embodiment, when both audio andvideo streams are present in an application such as video conferencing,full quality and data transfer rate of the audio stream may bepreserved, while adapting data transfer rate of the video stream basedon available residual bandwidth.

Performance enhancer 292 may generate media streams 312 for multiplelinks (and/or paths) 298 in step 384 based at least on matching datatransfer rate of each media stream 312 to available bandwidth across thecorresponding interface. Alternatively, performance enhancer 292 maygenerate a channel-coded stream in step 386 and disperse thechannel-coded stream into media streams 312 across multiple interfacesin step 388 based at least on matching the data transfer rate of eachmedia stream 312 to available bandwidth across the correspondinginterface. Media streams 312 may be transmitted across multipleinterfaces 26 in step 390.

Turning to FIG. 10, FIG. 10 shows a flow-chart illustrating exampleoperational steps that may be associated with a method 400 for enhancingtraffic of multiple media streams 312 according to an embodiment of thepresent disclosure. When multiple media streams 312 share a commonwireless bottleneck link, bandwidth may be allocated among themaccording to their media characteristics instead of conventionalfair-rate allocation. For example, when a media stream 312 showinghighly dynamic scenes from a motion movie competes against ahead-and-shoulder news clip destined for a mobile phone, higher datatransfer rate may be allocated for the former stream to maintain itsbasic quality.

In FIG. 10, voice/video stream 302 is incoming in step 402. Metainformation is extracted from voice/video stream 302 by meta informationextractor 290 in step 404. Connectivity of transmission interfaces iscalculated and/or predicted by performance enhancer 292 in step 406. Instep 408, bandwidth across each interface is measured by path/link statemonitor 286 to estimate the available bandwidth over a given path. Datatransfer rate across each interface may be calculated by media awarerate allocation in step 410 based on several alternative mediacharacteristics (i.e., media-aware criteria), including criteria tominimize the weighted sum of distortion of all participating mediastreams 312 across all interfaces and maintain equal quality of allparticipating media streams 312. Quality metrics or media-aware criteriacan either be objective, e.g., commonly adopted measurements based onpeak-signal-to-noise-ratio (PSNR), or subjective, based on extensiveprior study of user preference for various artifacts in a decoded videocontent. Thus, the data transfer rate allocated to each media stream 312may depend on its media characteristic, the receiver display size, aswell a total bottleneck bandwidth shared by all media streams 312.Performance enhancer 292 may calculate data transfer rate across eachinterface by matching data transfer rate to available bandwidth in step412.

Performance enhancer 292 can generate media streams 312 for multiplelinks (and/or paths) 298 in step 414 based at least on matching datatransfer rate of each media stream 312 to available bandwidth across thecorresponding interface. Alternatively, performance enhancer 292 maygenerate a channel-coded stream in step 416 and disperse thechannel-coded stream into media streams 312 across multiple interfacesin step 418 based at least on matching data transfer rate of each mediastream 312 to available bandwidth across the corresponding interface.Media streams 312 are transmitted across multiple interfaces in step420.

Turning to FIGS. 11 and 12, FIGS. 11 and 12 show a potential principleof operation of a traffic optimization method according to an embodimentof the present disclosure. FIG. 11 shows a graph of quality over datatransfer rate of two media streams 425 and 426. Quality of media stream425 is higher than quality of media stream 426 for a given data transferrate. Conversely, for a given quality, data transfer rate of mediastream 425 is lower than rate of media stream 426. Additionally, ifmedia stream 425 is transmitted at a rate r1 and media stream 426 istransmitted at a rate r2, the total rate, r1+r2, should be lower than orequal to available bandwidth ‘c’ of the link (i.e., r1+r2 c).

FIG. 12 shows a simplified diagram illustrating a potential principle ofoperation of embodiments according to the present disclosure. Two mediastreams, 425 and 426 with rates r1 and r2 respectively, traverse anetwork communication link symbolized by a pipe 428. Pipe 428 has abandwidth represented by ‘c.’ Media streams 425 and 426 may be directedto two different network devices, for example, a mobile phone and alaptop respectively. The total data transfer rate (i.e., r1+r2) ismatched to the total bandwidth (i.e., c) of the wireless link.

Turning to FIG. 13, FIG. 13 shows a flow-chart illustrating exampleoperational steps of a method 430 associated with efficient errorprotection when transmitting streams across multiple networks, accordingto an embodiment of the present disclosure. According to an exampleembodiment, efficient error protection may be achieved bydifferentiating error protection levels based on relative importance ofdifferent media packets and wireless channel conditions over eachwireless link. To ensure quality of traffic flow, important data streamsmay have to arrive at a receiver despite any underlying packet losses inthe wireless link. Conversely, quality of traffic flow may not benegatively impacted if less important packets do not arrive. These lessimportant media packets may be skipped if they are not successfullytransmitted the first time, while retransmission for more importantpackets may be performed to ensure that the important packets arrive.Thus, to ensure timely delivery of media packets, the number ofretransmissions may be limited based on a relative importance of thedata packets. For example, for streaming applications with a morelenient latency requirement than non-streaming applications, it may bemore efficient to combat packet losses via retransmissions, as opposedto forward error correction (FEC).

In FIG. 13, voice/video stream 302 is incoming in step 432. Metainformation is extracted from voice/video stream 302 by meta informationextractor 290 in step 434. Connectivity of transmission interfaces arecalculated and/or predicted by performance enhancer 292 in step 436.Performance enhancer 292 can generate media streams 312 for multiplelinks (and/or paths) 298 in step 438 based at least on matching datatransfer rate of each media stream 312 to available bandwidth across thecorresponding interface. Alternatively, performance enhancer 292 maygenerate a channel-coded stream in step 440. Performance enhancer 292may disperse the channel-coded stream into media streams 312 acrossmultiple interfaces in step 442 based at least on matching data transferrate of each media stream 312 to available bandwidth across thecorresponding interface. Media streams 312 are transmitted on multipleinterfaces 26 in step 444.

Proper transmission of media streams 312 is checked by path/link statemonitor 286 in step 446. For example, if a Transmission Control Protocol(TCP) is used to transport data packets between OBU 30 and networkcontroller 284, proper transmission can be checked from acknowledgement(ACK) packets sent back by a receiver (i.e., a node, either OBU 30 orcontroller 284, that receives data packets).

If it is determined that there is packet loss (i.e., one or more packetsin media stream 312 have not reached a receiver), a retransmission levelbased on media characteristics may be calculated by performance enhancer292 in step 448. In one embodiment, 3G and 4G wireless channels thatallow both radio link control (RLC) frame retransmissions and mediumaccess control (MAC) frame retransmissions may be used. In anotherembodiment, Wireless Local Area Network (WLAN) that allows MAC frameretransmission may be used. According to embodiments of the presentdisclosure, the retransmission level can be dynamically tuned based onvarious factors, including meta information 306, such as relativeimportance of each packet, latency requirement of applicationoriginating voice/video stream 302, decoding deadline of each packet, orexpected channel condition over each link or codependency amongsuccessfully delivered and in-transit packets, or a combination thereof.

If the calculated retransmission limit is not met as determined in step450, the packet is retransmitted in step 452. For example,retransmission of streaming video data may be performed for I-framepackets, which have a highest relative priority, up to N times, whileretransmission of P-frame packets may be limited to M (M<N), andretransmission of B-frame packets, which have a lowest relativepriority, may not be performed at all. Optimization of retransmissionlevels may be combined with intelligent interface selection (e.g., pathassignment), for instance, by always choosing to send the most importantpackets over a link with lowest observed packet loss rate. If there isno packet loss in step 446, and/or if the calculated retransmissionlevel is met as determined in step 450, transmission terminates in step454.

Turning to FIG. 14, FIG. 14 is a simplified block diagram illustrating apotential principle of operation of performance enhancement of dataaccording to an embodiment of the present disclosure. Diversity acrossalternate multiple wireless links (and/or paths) 298 may be leveraged tomitigate an impact of bursty packet losses over any particular link(and/or path). In one example implementation shown in FIG. 14, crucialpackets 462 in an incoming data stream 302 may be duplicated duringtransmission over multiple wireless links (and/or paths) 298. In exampleembodiments, crucial packets 462 may include packets containing motionvectors and I-frames in compressed video, and base-layer packets in ascalably encoded audio or video stream. Thus, duplication of crucialpackets 462 may ensure that crucial packets arrive losslessly at areceiver as compared to less crucial packets.

Turning to FIG. 15, FIG. 15 is a simplified block diagram illustrating apotential principle of operation of performance enhancement of dataaccording to an embodiment of the present disclosure. In general,channel coding deals with error control techniques. If data at an outputof a communication system has a high error rate, coding may permit anincreased rate of information at a fixed error rate, or a reduced errorrate at a fixed transfer rate. In general, when a data stream is coded,a decoder can determine errors by checking if the received word is avalid code word or corrupted by noise.

In accordance with embodiments of the present disclosure, erasureprotection channel coding and error protection channel coding, such asReed-Solomon (RS) code, may be implemented across an incoming datastream 302, to create channel-coded stream 464. For example, a videostream 302 may be partitioned into segments, with each segmentcontaining m packets. A block code may be applied to the m packets togenerate additional r redundant packets (i.e., parity packets) resultingin an n-packet block, where n=m+r. With such coding, a receiver canrecover the original m packets if a sufficient number of packets in ablock are received. According to the present embodiment, channel codedstream 464 may be dispersed into coded packets 468 and uncoded packets470 and dispersed across multiple links (and/or paths) 298. Uncodedpackets 470 may also be transmitted concurrently with codes packets 468to decode coded packets 468.

Turning to FIG. 16, FIG. 16 is a flow-chart illustrating exampleoperational steps of a method 480 associated with robust packagedelivery according to an embodiment of the present disclosure.Voice/video stream 302 is incoming in step 482. Meta information isextracted from voice/video stream 302 by meta information extractor 290in step 484. Connectivity of transmission interfaces 26 is calculatedand/or predicted by performance enhancer 292 in step 486. Performanceenhancer 292 can generate media streams 312 for multiple links (and/orpaths) 298 in step 488 based at least on duplicating crucial datapackets across multiple interfaces. Alternatively, performance enhancer292 may generate a channel-coded stream in step 490, for example, byadding error codes (i.e., parity packets) to data packets to createcoded packets 468. Performance enhancer 292 may disperse thechannel-coded stream into media streams 312 across multiple interfacesin step 492. Duplication or channel coding of data may introduce acertain level of redundancy in transmitted media streams 312. Suchredundancy may be carefully tuned to balance any tradeoff betweenrobustness and overhead in step 494. Tuning of redundancy level may beperformed based on one or more factors, including observed wirelesschannel conditions over each wireless link; amount of crucialinformation embedded in each media stream 312; and effectiveness oferror concealment mechanisms used in communication system 10. Mediastreams 312 are transmitted on the interfaces in step 496.

Thus, multiple audio and video streams may be sent or received inside avehicle. When multiple audio applications are sent or received inside avehicle, for example, simultaneous use of a radio and a videoconferencing system, there may be a need to use noise cancellationtechniques to enhance audio quality. For example, beamforming of voicewith multiple speakers may be implemented followed by active noisecancellation with multiple microphones to cancel ambient noise andimprove audio quality.

Beamforming is a signal processing technique used for directional signaltransmission or reception involving combining audio signals frommultiple microphones in such a way that signals at a particular angleexperience constructive interference and signals at other anglesexperience destructive interference. Beamforming can be used at bothtransmit and receive to achieve spatial selectivity. Thus, whentransmitting, a phase and relative amplitude of the signal at a senderare controlled to create a pattern of constructive and destructiveinterference in a wavefront of the sound signal. When receiving,information from different sensors (e.g., microphones) is combined suchthat the expected pattern of radiation is preferentially observed.

Turning to FIG. 17, FIG. 17 is a simplified block diagram of an exampleinterior of a vehicle, such as vehicle 4 showing exemplary placement ofOBU 30, microphones and speakers in communication system 10 according toan embodiment of the present disclosure. Because OBUs may have variouscollaboration applications such as VoIP, Cisco WebEx®, CiscoTelepresence®, Voice-to-Text, Text-to-Voice applications, and the like,the interior of the vehicle may have noise originating from varioussources that interferes with the quality of speech of hands freemicrophone and speaker systems. A signal processing module 502 in OBU30, together with strategically placed microphones 504 a-f and speakers506 a-f, can improve speech quality in noisy vehicular environments bysuppressing multiple sources of background noise, sounds and echoes.Communication system 10 may also automatically cause adjustments tovoice volume and equalization, and may employ beamforming techniques tomaximize speech quality.

One or more microphones 504 a-f and one or more speakers 506 a-f may beemployed for adaptive noise cancellation and acoustic beam-forming.Microphones 504 a-f and speakers 506 a-f can be built-in systems forvehicle 4 and/or mobile devices such as smartphones and tablets.Microphones 504 a-f can send acoustic signals to OBU 30 over acommunication link 512 that may be wired or wireless inclusive of anyelectronic link. Examples of wired links include USB cable, HDMI cable,Ethernet, Controller Area Network (CAN) buses, Local Internet Network(LIN) buses and Media Oriented System Transport (MOST) buses. Examplesof wireless links include IEEE 802.11, 802.16, WiFi, Bluetooth, andWiMax. Similarly, processed acoustic signals may be sent from OBU 30 tospeakers 506 a-f over wired or wireless communication links.

In accordance with embodiments of the present disclosure, one or moremicrophones (not shown) may be positioned outside a car, for example,near an engine or exterior noise area, to select noise frequency bands.Microphones 504 a maybe positioned near the driver, for example, on asteering wheel 514. Similarly, microphones 504 b may be positioned neara passenger seat area to capture the passenger's speech on a hands-freetelephone call. If the driver is speaking, the corresponding microphone504 a can be used as a source of speech with beamforming, dynamic voiceequalization and volume adjustment to improve energy of an inputfrequency band of the speech. The remaining microphones 504 b-f can beused as noise sources to filter out noise surrounding the speaker,including stationary and non-stationary noise, intermittent ambientsounds and echoes. For example, the remaining microphones 504 b-f mayprovide noise cancellation, wherein sound waves from some microphonesinterfere with and cancel sound waves from other microphones, therebyreducing noise.

These dual techniques (i.e., beamforming and active noise cancellationtechniques) can provide a clear voice to a listener on a remote node ora clear voice input to a voice-to-text engine residing in OBU 30. Itwill be appreciated that although the embodiment has been described withrespect to microphones, the methods described herein are applicable tosituations wherein one or more users may be listening to audio frommultiple speakers 506 a-f. In such cases, beamforming may be used totransmit high quality audio for a high priority user or application. Forexample, a traffic alert audio may have higher priority than musicplaying over all speakers. Beamforming may be used to direct the trafficalert signal to speakers 506 a near the driver to enhance the trafficalert audio quality over the music.

Turning to FIG. 18, FIG. 18 illustrates a flow-chart illustratingexample operational steps that may be associated with a method 520cancelling noise in a vehicular network environment according toembodiments of the present disclosure. Method 520 begins in step 522. Instep 524, audio is input into a microphone 1. For example, a passengermay initiate a conference call using a hands-free telephone systemequipped in vehicle 4. Microphone 1 may be situated close to thepassenger initiating the conference call. Other microphones in vehicle4, for example, microphones 2 to N, may receive the audio streams instep 526. Audio signals from microphones 2 to N may be sent to OBU 30,which analyzes the sound wave signals in step 528 to determine thesource of sound, in this case, microphone 1. OBU 30 may enhance voicequality of sound from microphone 1 in step 530. Voice enhancement may beperformed according to one or more techniques, for example, dynamicvoice equalization or volume adjustment or a combination thereof, toimprove quality of audio from microphone 1, while suppressing noise andambient sounds from microphones 2 to N. The enhanced audio istransmitted to a remote end node by the OBU 30 in step 532, and theprocess is terminated in step 534.

In example embodiments, a HUD can display a picture of a vehicle, forexample, vehicle 4. The picture on the HUD can be used to select aprimary application, and a corresponding user, for example a driver, maychoose a driver's seat position on the picture to instruct OBU 30 thatthe driver wants to listen to the radio. Simultaneously, a passenger inthe back may choose a back seat on the picture to instruct OBU 30 thatthe passenger wants to use a WebEx application. OBU 30 can use thisinformation from the driver and passenger to provision microphones,speakers and other components of the vehicle appropriately for each userand chosen application. Thus, the speakers in the front may beconfigured to transmit audio from the radio application, whilesuppressing noise from the speakers in the back. Simultaneously,speakers in the back may be configured to transmit audio from the WebExapplication while suppressing noise from the speakers in the front.

In another example, radio controls may be exclusively in the front, andWebEx controls may be exclusively in the back. When a user selects radiocontrols, OBU 30 can automatically determine that microphones, speakersand other components of the vehicle in the front may be activated. Onthe other hand, when a user selects WebEx controls, OBU 30 canautomatically determine that microphones, speakers and other componentsof the vehicle in the back may be activated.

Thus according to embodiments of communication system 10 describedherein, a user in a vehicle may receive multiple data streams, includingaudio and video, from various sources inside and outside a vehicle. Inresponse, or to provide commands to in-vehicle devices, for example, avideo conferencing system, or for other purposes, the user may want toinput data or information or commands into OBU 30 or other devices. Forexample, the user may want to initiate and conduct a video conferencingcall in a vehicle. In another example, a user may want to control avolume of music playing from an audio system in the vehicle. Identityprofiles associated with the user may be used to store user commandsand/or preferences for various user inputs.

Turning to FIG. 19, communication system 10 depicts further details thatmay be associated with OBU 30. In accordance with embodiments ofcommunication system 10, OBU 30 may be provisioned with one or moreidentity profiles 34 a, 34 b, and 34 c (referred to collectively hereinas identity profiles 34), with each identity profile 34 corresponding toan agent that can authenticate to OBU 30. Identity profiles 34 caninclude profile information for a particular agent.

Profile information may be configured to aggregate agent attributes,account information, preferences, and/or settings, which can enableappropriate transactions by authenticated agents. For example, profileinformation can include vehicle settings, dashboard preferences, usercommands (e.g., voice commands, gesture commands), applicationpreferences (e.g., radio station preferences for driver and passengers,preferences regarding applications preferred by users in particularseats, etc.), wireless interface preferences (e.g., WiFi accountinformation, etc.), web account information (e.g., multimedia, socialnetworking, etc.), mobile device list (e.g., smartphones, mobile phones,tablets, laptops, etc.) including network configurations for mobiledevices, network service provider membership account information,insurance information, credit card/payment account information,manufacturer web account information, network interface accountinformation, GPS favorite locations, and phone contact list.

The information included in a particular identity profile may be atleast partially dependent upon the particular agent to which itcorresponds. For example, an authorized entity (e.g., a manufacturer ofthe vehicle, etc.) may not need vehicle settings, GPS favoritelocations, or multimedia information in its identity profile. Inaddition to agents, a profile identity may be provisioned for a vehicleitself including information to distinctly identity the vehicle (e.g., avehicle identification number (VIN)). It will be apparent that theexamples provided herein of profile information are not all-inclusive,and any other suitable information or data could be included as profileinformation.

Various implementations can accommodate identity profiles 34 in OBU 30.For example, in one embodiment identity profiles 34 are stored indedicated hardware (e.g., physical SIM card, memory card, etc.).Software can be configured to virtually switch between differenthardware or the hardware itself may be programmable to store differentagent identity information over time. In another embodiment, identityprofiles 34 are stored in a programmable storage module or virtualidentity module that can store one or more identity profiles 34.Generally, identity profiles 34 may be kept in any suitable memoryelement, software, hardware, or in any other suitable component, device,element, or object where appropriate and based on particular needs. Inaddition, identity profiles 34 may be provided in any database,register, cache, queue, control list, or storage structure.

In example embodiments of the present disclosure, identity profiles 34may be provisioned and managed through one or more identity serviceproviders, who may be a third party service provider, a mobile networkoperator, a vehicle manufacturer, a vehicle rental and leasing agency, avehicle dealer, a government agency, or any other entity having aninterest in managing identities associated with a vehicle over the lifeof the vehicle. Moreover, identity profiles 34 can be managed throughthe same or different identity service providers. By storing an identityprofile in a remote cloud, for example, the identity profile can beassociated with an agent rather than a particular vehicle. Consequently,a human agent (e.g., driver, passenger, owner, renter, etc.) canretrieve his identity profile in any vehicle. Depending on themake/model of the vehicle, the human agent can leverage relevant partsof the identity profile for available features in virtually any vehicle.Identity profile 34 may be dynamically added, removed, and updated vialocal or remote network access.

In other example embodiments, an identity profile may be stored on atransportable memory element (e.g., USB stick, CD, etc.), which may beprovided locally to OBU 30 by a user. The identity profile can then bedownloaded to OBU 30 from the transportable memory element. In otherexample scenarios, an identity profile may be dynamically created andmanaged (e.g., removed or updated) locally, directly through OBU 30. Forexample, OBU 30 may provide an identity profile creation tool through adisplay for an end user 2 to enter desired profile information andassociate such information with an agent. In another embodiment, theidentity profile creation tool may be accessible through a user's mobiledevice. In these scenarios, the identity profile would not be accessiblethrough identity service providers and could only be accessed in theparticular vehicle containing the identity profile.

Turning to FIG. 20, FIG. 20 shows various example embodiments of agesture based user interface. User interface 536 may be a touch pad(e.g. single touch, multi touch) based input device mounted on steeringwheel 514 of vehicle 4 and connected to OBU 30. OBU 30 may be configuredto direct media information to one or more appropriate displays (e.g.,display 28) in vehicle 4, and may be further configured to compute touchinputs from gesture based user interface 536 based on displayedinformation on the appropriate corresponding display.

FIGS. 20( a) and 20(b) illustrate single and multi touch operations ofgesture based user interface 536 mounted on steering wheel 514. Userinterface 536 may sense and respond to gestures in the form of one ormore touches. Thus, user 2 may touch user interface 536 to implementuser commands such as click, select, drag up/down/left/right, zoom inand out, flip, swipe, pan, expand, minimize, go forward/backward, etc.Example touches may include pressing, tapping, rotating a wheel on asurface 538 of user interface 536, moving one finger over surface 538 ofuser interface 536, moving multiple fingers over surface 538 of userinterface 536, etc. These and other possible touches can be used tocontrol different applications and in-vehicle devices, such asin-vehicle climate, audio and video, navigation, infotainment systems,etc.

In another example embodiment according to the present disclosure, akeyboard and/or number pad 540 can also be mounted on steering wheel 514as illustrated in FIGS. 20( c) and 20(d). A driver familiar with alayout of keyboard/number pad 540 can type words or numbers whilekeeping his/her eyes on the road. Smart predictive text/number input canaugment user interface 536 so that the driver can input a minimum numberof characters. In such a scheme, one or more predicted words may appearon a screen for the driver to select. The driver may select theappropriate text or number using one or more appropriate touches on userinterface 536. It will be appreciated that the type and layout ofkeyboard/number pad 540 illustrated in FIGS. 20( c) and 20(d) are forexample purposes only. Other variations and designs may be implementedwithout changing the scope of the disclosure. For example, keyboard 540may be split into two halves, and each half may be located on eitherside of steering wheel 514. User interface 536 may be mounted on otherparts of the vehicle, for example, adjacent to steering wheel 514, on adashboard, etc. It will be appreciated that various placements anddesigns of user interface 536 are possible without changing the scope ofthe present disclosure.

Turning to FIG. 21, FIG. 21 shows a flow-chart illustrating exampleoperational steps that may be associated with a method 560 for operatinga touch based user interface 536 according to an embodiment of thepresent disclosure. Method 560 starts in step 562. In step 564, user 2may touch user interface 536, for example, swipe the user's index fingerfrom right to left on surface 538 of user interface 536. OBU 30 maysense this gesture command from the user through user interface 536. OBU30 may determine which display is associated with user interface 536 instep 566. OBU 30 can evaluate information on the display correspondingto user interface 536 in step 568.

For example, OBU 30 may aggregate signals from the user's touch inputsto effect actions on multiple applications. Multiple applications may besimultaneously running on OBU 30, and/or on multiple in-vehicle devices.At any given time, one application of the multiple applications may bedisplayed as a primary application on a heads up display (HUD) orin-vehicle display. In one example embodiment, user 2 may pre-select thedesired display to be controlled by inputs through gesture based userinterface 536. For example, icons representing different displays may beavailable for selection on a primary display such as HUD. By default,user interface 536 may control the HUD only and user 2 can select anappropriate icon of choice to switch the primary display from HUD toanother in-vehicle display. Once switched to the desired display, user 2can select a different icon using user interface 536 to switch tocontrolling a different primary display.

In another example embodiment, camera(s) tracking a driver's eyes maydetermine the primary display. In yet another example embodiment, OBU 30may share resources with in-vehicle devices such as smart phones,laptops, tablets, etc. For example, OBU 30 may use a phone's screen as adisplay. With seamless resource sharing, in-vehicle devices can utilizeuser interface 536 as an input device to control applications on thein-vehicle device. In a particular example, a smartphone sharingresources with OBU 30 may be controlled by user interface 536.

In step 570, OBU 30 may check whether identity profile 34 correspondingto user 2 is available. In example embodiments of the presentdisclosure, user inputs may be associated with identity profiles 34 a-c.For example, identity profile 34 a may be associated with a first user,34 b may be associated with a second user, and identity profile 34 c maybe associated with a third user. A swipe on surface 538 of userinterface 536 by the first user with identity profile 34 a may beinterpreted differently by OBU 30 than the same swipe by the third userwith identity profile 34 c.

In other example embodiments, touches may be customized to a user'sgender, for example, a woman's touches may be interpreted differentlyfrom a man's touches. In other example embodiments, touches may beassociated with user age. For example, an adult's touches may beinterpreted differently from a teenager's touches. In other exampleembodiments, touches may be based on generic human behavior, independentof identity profiles associated with specific users. Such touches basedon generic human behavior may be stored in default identity profiles.For example, a swipe of an index finger to the left by any user (i.e.,irrespective of any identity profile 34) may be interpreted to mean thatthe user wants to move the display to the left. It will be apparent thatthe examples provided herein of associations between touches andactions/interpretations and/or identity profiles 34 are notall-inclusive, and any other suitable associations could be includedbetween touches, actions/interpretations and identity profiles.

OBU 30 may also determine user input, such as smart text and predictiveactions, from the user's touches based on a user context for the primaryapplication. For example, if user 2 has selected a radio playing musicon a radio station, then a few swipes on surface 538 of user interface536 may imply that user 2 probably wants to tune the radio to anotherradio station. In another example, user 2 may select a phone, and thesame swipes on surface 538 of user interface 536 may imply that user 2wants to redial a previously called number. It will be appreciated thatnumerous other scenarios are possible for context based determination ofuser inputs.

If identity profile 34 is not available, OBU 30 can interpret user'stouch, based on a default profile and primary application in step 574.On the other hand, if an identity profile 34 for user 2 is available,OBU 30 may interpret user's touches based on the corresponding identityprofile 34 and primary application in step 576. OBU 30 can sendcontrolling signals based on interpretations of user's touch to theappropriate primary application, in-vehicle device, remote node, etc. instep 578. The process ends in step 580.

In accordance with embodiments of the present disclosure, other gesturesmay also be used to input user commands and send signals via appropriateuser interfaces. Turning to FIG. 22, FIG. 22 illustrates a simplifiedblock diagram of gesture based user interfaces 582 a-d in communicationsystem 10 according to embodiments of the present disclosure. Gesturesmay be expressed using hands, fingers, head, eyes and/or other parts ofthe body either alone or in combination. Gestures may also be used incombination with physical objects, icons and pictures. For example, ahand wave may be interpreted as a signal to stop a phone application,whereas the hand wave in combination with a head nod and a picture maybe interpreted as a signal to start a phone application and dial aspecific number.

In accordance with embodiments of communication system 10, OBU 30 may beprovisioned with one or more gesture based user interfaces 582 a-d(referred to collectively herein as gesture based user interfaces 582),with each gesture based user interface 582 adapted to communicate withOBU 30 via wireless links. Examples of wireless links include IEEE802.11, 802.16, WiFi, Bluetooth, and WiMax. Gesture based user interface582 may be: 1) an electronic wearable device, or an object attached toan electronic device, for example, a camera, illustrated in FIG. 22 asgesture based user interface 582 a; or 2) image recognition viaappropriate sensors and devices.

According to embodiments of the present disclosure, a user may wear agesture based user interface 582 whose motion and orientation representdifferent types of inputs. Example devices include: rings, watches,wristbands, earrings, headbands, etc. In each case, an electroniccircuit comprising accelerometers, gyroscopes, batteries, compasses, andwireless transceivers can be imbedded in user interface 582, which maybe active or passive. As used herein, ‘active devices’ can wirelesslytransmit signals representing motion information to OBU 30. An exampleof an active device, illustrated in FIG. 22 as gesture based userinterface 582 b, may be a wristband comprising an accelerometer 584,gyroscope 586, compass 588, wireless transceiver 590, storage unit 592,and battery 594. Accelerometer 584, gyroscope 586 and compass 588 trackmotion and orientation of the user interface 582 b. Wireless transceiver590 may transmit the motion and orientation information to OBU 30wirelessly, for example, using Bluetooth, WiFi Direct, or other wirelesstechnologies.

As used herein, ‘passive devices’ do not transmit information to OBU 30.Rather, one or more passive devices, one or more detectors, and/orsensors coupled to OBU 30 track movements of the one or more passivedevices and thereby capture gestures. An example of a passive deviceenabling gesture commands, illustrated in FIG. 22 as user interface 582c, is radio frequency identification (RFID) tag with corresponding RFIDreaders to detect RFID signals. RFID tags may be embedded in physicalobjects, icons, or pictures. OBU 30 may aggregate information from oneor more active devices and/or detectors/sensors detecting motion of oneor more passive devices to determine a desired user input from theuser's gestures.

Gestures may be used to control applications and in-vehicle devices, forexample, selecting projected icons or information on a windshield HUD,flipping to a next set of icons or information on the HUD, andcontrolling audio and climate settings. In another example embodiment,user 2 may use multiple user interfaces 582 (e.g., multiple rings ondifferent fingers) to aggregate more information to OBU 30. For example,user 2 may wear multiple rings on different fingers, so that differentfinger orientations and gestures can represent predetermined set ofinputs (e.g. speed dial a phone number via gesture). In anotherembodiment, user 2 may wear a passive RFID tag ring on one finger ormultiple passive RFID tag rings on different fingers. One or more RFIDreaders can capture the location and orientation of the RFID tags andtransmit that information to OBU 30. In yet another embodiment, user 2may wear an RFID reader. Multiple RFID tags may be distributed aroundvehicle 4 to reflect signals back to the RFID reader so that OBU 30 candetermine its relative location and motion.

Turning to FIG. 23, FIG. 23 is a simplified diagram of a userinteracting with example components associated with a gesture based userinterface 582 in communication system 10 according to an embodiment ofthe present disclosure. User 2 may wave an article 596 embedded withRFID logic. Article 596 may be a picture, or icon, or object. An RFIDreader 598 may capture RFID information from article 596 and relay theRFID information to OBU 30. OBU 30 may associate a correspondingpreprogrammed input indicating an intent of the object being waved orotherwise moved, and may interpret the gesture as appropriate input bythe user. For example, user 2 may wave a picture of a person, forexample, her daughter, the picture being attached with an RFID tag. AnRFID reader may capture the RFID information and transmit the RFIDinformation to OBU 30. An application on OBU 30, for example, a phoneapplication, can register the RFID information and associate it with thedaughter's phone number. The phone application can then automaticallydial the phone number. In another example, user 2 may hold differentobjects in front of a camera to trigger preprogrammed responses. Forexample, a red cube may signal calling home, a yellow triangle maysignal calling another person, etc.

Turning to FIG. 24, FIG. 24 illustrates further gesture based userinterfaces 582 in communication system 10 according to embodiments ofthe present disclosure. According to example embodiments, informationabout gestures can be aggregated through image recognition techniques.For example, as illustrated in FIG. 24( a), one or more cameras 602 maybe positioned opportunistically inside vehicle 4 to record gestures fromuser 2 by capturing images of user 2. The captured images can be sent toOBU 30 for image recognition processing including, for example, featureextraction and gesture estimation. Cameras 602 may be optical, infrared,time-of-flight or any suitable combination thereof to capture variousinformation associated with gestures, for example speed and type ofgesture. One or more image-based recognition techniques could be usedwith standard off-the-shelf cameras. However, time-of-flight cameras mayprovide additional depth information that can make feature and gestureextraction more accurate and reliable.

In example embodiments, gestures may also be context sensitive.Generally, gestures could be predefined as representing a particularcommand or having a particular meaning when used in different contexts.Thus, the same gesture could indicate one command in a first context andcould indicate a different command in a second context. For example,user 2 may be asked by an application to select icons displayed on theHUD. A pointing motion by user 2 may mean icon selection whereas aswiping motion may mean flipping to the next set of icons. On the otherhand, when dialing a call, a pointing motion may mean a particularnumber, whereas a swiping motion may mean switching call recipients.

Cameras 602 may be mounted in several locations. In one exampleembodiment, as illustrated in FIG. 24( b), camera 602 may be located ona seat belt of user 2 to provide “driver's eye view” of a driver's handsand body for gesture recognition. In another example embodiment, asillustrated in FIG. 24( c) camera 602 may be located on steering wheel514 for hand and body gesture recognition. In yet another exampleembodiment, camera 602 may be mounted on a sun visor to get a clear viewof the driver's head and eyes and calculate the direction of thedriver's line of sight. In another example embodiment, camera 602 may belocated on a passenger side of a dashboard to get a profile view andenhance tracking and gesture extraction accuracy. In another exampleembodiment, camera 602 may be located on an exterior of the vehicle toprovide sensory data about the environment. Such image based recognitionmay allow OBU 30 to provide better information based on passive datacollected about the driver. For example, a time-of-flight camera 602 cancalculate the direction a driver is looking, and can select to displayinformation on a HUD at an unobtrusive location away from the driver'sdirect line of sight. In other examples, image based recognition can beused to detect a critical event (e.g., event creating potential dangerto the driver and/or others) and alert the driver of such events.

Turning to FIGS. 25-28, FIGS. 25-28 illustrate various flow chartsillustrating example operational steps associated with a method 610using multiple user interfaces according to embodiments of the presentdisclosure. According to various embodiments, in method 610, one or moreuser interfaces may be used simultaneously or in conjunction with eachother. In FIG. 25, method 610 starts in step 612 and illustrates anexample scenario. Camera 602 may detect that a driver is looking out aside window in step 620, at the same time that a rangefinder sensor 14on a front bumper may detect that an object has just moved into a pathof vehicle 4 in step 622. OBU 30 can aggregate information from camera602 and rangefinder sensor 14 and may send controlling signals to anaudio system in step 624. The audio system may issue an audible alert instep 626 to alert the driver about the object. The process ends in step660.

In FIG. 26, method 610 starts in step 612 and illustrates anotherexample scenario. An infrared camera 602 may sense in step 628 that adriver's body temperature is dropping at around the same time that atime-of-flight camera 602 may capture the driver's head drooping in step630. OBU 30 can aggregate information from the infrared camera andtime-of-flight camera and may send controlling signals to an audiosystem and temperature controls in step 632. In response, thetemperature controls can adjust vehicle internal temperature in step 634and the audio system can simultaneously issue an audible alert in step636 to wake up the driver as he begins to doze off, and make automaticadjustments to a climate control or stereo to keep the driver awake andalert. The process ends in step 660.

In FIG. 27, method 610 starts in step 612 and illustrates yet anotherexample scenario. A camera 602 may detect movement across its viewcaused by a lighting change (e.g., when the vehicle enters a tunnel) instep 638. OBU 30 may cross-reference the lighting change informationwith a ring accelerometer 582 worn on a user's finger, which does notdetect motion in step 640. OBU 30 may determine that the user's hand hasnot moved and no gesture should be inferred in step 642. Vehicle 4 maybe equipped with a touch based user interface 536 and gesture based userinterface 582. The process ends in step 660.

In FIG. 28, method 610 starts in step 612 and illustrates a furtherexample scenario. Assume that user 2 cannot move his fingers to usetouch based user interface 536 (e.g., user 2 is focusing on the road andcannot take his hands or fingers away from the steering wheel). However,a camera 602 may detect that the driver is focused on the road, andnodding his head in step 644, while user interface 536 does not detecttouch in step 646. Accordingly, OBU 30 may dynamically switch to gesturebased user interface 582 in step 648. In step 650, OBU 30 may interpretuser gestures based on suitable identity profile 34 and a primaryapplication. OBU 30 may send controlling signals to the primaryapplication in step 652, and the primary application may respond in step654. The process ends in step 660.

It will be appreciated that while method 610 has been described withreference to various steps in connection with FIGS. 25-28 that may occurin certain example scenarios as a user operates a vehicle, the stepstherein are not comprehensive and may include numerous other movementdetections and appropriate responsive signals to a primary application,to vehicle settings, to an audio system, and the like. Additionally,while FIGS. 25-28 illustrate operations associated with particularmovement and sensory detections, any movement and sensory detectionscould be combined and therefore, countless scenarios may be possible.Moreover, the movement and sensory detections can be achieved using anysuitable combination of one or more user interfaces of the same ordiffering types.

In certain implementations and numerous examples provided herein,vehicle 10 is described with reference to an automobile. Communicationsystem 10, however, is not limited to automobiles, but can be applied toa myriad of other types of vehicles (e.g., airplanes, boats, trains,etc.). It will be appreciated that the broad teachings disclosed hereinare intended to include any type of vehicle used to move from onelocation to another location, including vehicles that are not designedto transport humans.

In one example implementation, the on-board unit (OBU) (e.g., OBU 30)and controller (e.g., controller 284) are network elements thatfacilitate or otherwise help coordinate mobility events, networkconnectivity, and the transmission of data packets (e.g., for mobiledevices, for machine devices, for nodes, for end users, or for a networksuch as those illustrated in the FIGURES herein) associated with avehicular network environment. As used herein, the term ‘networkelement’ is meant to encompass computers, network appliances, servers,routers, switches, gateways, bridges, loadbalancers, firewalls,processors, modules, or any other suitable device, component, element,or object operable to exchange information in a network environment.Moreover, the network elements may include any suitable hardware,software, components, modules, interfaces, or objects that facilitatethe operations thereof. This may be inclusive of appropriate algorithmsand communication protocols that allow for the effective exchange ofdata or information.

In example implementations, at least some portions of the internalnetworking, data optimization and dynamic frequency selection activitiesoutlined herein may be implemented in software in, for example, the OBUand/or controller. In some embodiments, one or more of these featuresmay be implemented in hardware, provided external to these elements, orconsolidated in any appropriate manner to achieve the intendedfunctionality. The OBU and controller may include software (orreciprocating software) that can coordinate in order to achieve theoperations, as outlined herein. In still other embodiments, one or bothof these elements may include any suitable algorithms, hardware,software, components, modules, interfaces, or objects that facilitatethe operations thereof. Furthermore, OBUs described and shown herein mayalso include suitable interfaces for receiving, transmitting, and/orotherwise communicating data or information in a network environment.Additionally, some of the processors and memory elements associated withthe various network elements may be removed, or otherwise consolidatedsuch that a single processor and a single memory location areresponsible for certain activities. In a general sense, the arrangementsdepicted in the FIGURES may be more logical in their representations,whereas a physical architecture may include various permutations,combinations, and/or hybrids of these elements.

It is imperative to note that, because of the inherent properties of thetechnologies being leveraged by the present disclosure, the terms‘node’, ‘network element’, ‘OBU’, and ‘controller’ are broad and,therefore, inclusive of many of the equipment examples discussed herein(e.g., a router, a wireless mobile device, a gateway, etc.). Suchexpansive breadth is afforded to this terminology due to the flexibilityof the presented architectures (e.g., components can be readilyexchanged for alternatives). Moreover, there are countless possibledesign configurations that can be used to achieve the operationalobjectives outlined here. Accordingly, the associated infrastructure hasa myriad of substitute arrangements, design choices, devicepossibilities, hardware configurations, software implementations,equipment options, etc. In addition, the terms ‘node’, ‘networkelement’, ‘OBU’, and ‘controller’ share overlapping definitions as usedherein in this Specification, where particular scenarios andenvironments may require these elements to be extended to specificdevice provisioning that is atypical. At least in a general sense, theseterms are interchangeable due to the limitless schemes in which they canbe deployed.

Note that with the numerous examples provided herein, interaction may bedescribed in terms of two, three, four, or more network elements.However, this has been done for purposes of clarity and example only. Itshould be appreciated that the system can be consolidated in anysuitable manner. Along similar design alternatives, any of theillustrated computers, modules, components, and elements of the FIGURESmay be combined in various possible configurations, all of which areclearly within the broad scope of this Specification. In certain cases,it may be easier to describe one or more of the functionalities of agiven set of flows by only referencing a limited number of networkelements. It should be appreciated that communication system 10 of theFIGURES and its teachings are readily scalable and can accommodate alarge number of components, as well as more complicated/sophisticatedarrangements and configurations. Accordingly, the examples providedshould not limit the scope or inhibit the broad teachings ofcommunication system 10 as potentially applied to a myriad of otherarchitectures.

It is also important to note that the operations and steps describedwith reference to the preceding FIGURES illustrate only some of thepossible scenarios that may be executed by, or within, the system. Someof these operations may be deleted or removed where appropriate, orthese steps may be modified or changed considerably without departingfrom the scope of the discussed concepts. In addition, the timing ofthese operations may be altered considerably and still achieve theresults taught in this disclosure. The preceding operational flows havebeen offered for purposes of example and discussion. Substantialflexibility is provided by the system in that any suitable arrangements,chronologies, configurations, and timing mechanisms may be providedwithout departing from the teachings of the discussed concepts.

Although the present disclosure has been described in detail withreference to particular arrangements and configurations, these exampleconfigurations and arrangements may be changed significantly withoutdeparting from the scope of the present disclosure. For example,although the present disclosure has been described with reference toparticular communication exchanges involving certain network access andprotocols, communication system 10 may be applicable to other exchangesor routing protocols in which packets are exchanged in order to providemobility data, connectivity parameters, access management, etc.Moreover, although communication system 10 has been illustrated withreference to particular elements and operations that facilitate thecommunication process, these elements and operations may be replaced byany suitable architecture or process that achieves the intendedfunctionality of communication system 10.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims.

What is claimed is:
 1. A method, comprising: establishing communicationchannels between an on-board unit (OBU) of a vehicle and a plurality ofnodes; receiving a plurality of data from the plurality of nodes;tagging each of the plurality of data with a respective priority level;storing the plurality of data in a priority queue according to therespective priority levels; storing a first data in a data store priorto storing the first data in the priority queue if the priority queue isfull and if each stored data in the priority queue is tagged with ahigher priority level; moving a stored data tagged with a lower prioritylevel from the priority queue to the data store if the priority queue isfull and if the first data is tagged with a higher priority level;selecting a medium to present the first data of the plurality of data toa user; and presenting the first data to the user via the medium,wherein the plurality of nodes includes a remote node and an in-vehicledevice.
 2. The method of claim 1, wherein the tagging each of theplurality of data with a respective priority level comprises:identifying a data type of the first data of the plurality of data;accessing a previously stored mapping of data types to correspondingpriority levels; and associating a priority level to the first data, thepriority level corresponding to the data type of the first data.
 3. Themethod of claim 2, wherein the previously stored mapping of data typesmay be set by a user preference.
 4. The method of claim 1, furthercomprising: determining that a first information of the first data and asecond information of a second data are related; and combining the firstdata containing the first information with the second data containingthe second information into a combined data, wherein the combined datais ordered in the priority queue.
 5. The method of claim 1, wherein thein-vehicle device is a sensor in the vehicle, wherein the remote node isa second on-board unit of a second vehicle.
 6. Logic encoded innon-transitory media that includes code for execution and when executedby a processor is operable to perform operations comprising:establishing communication channels between an on-board unit (OBU) of avehicle and a plurality of nodes; receiving a plurality of data from theplurality of nodes; tagging each of the plurality of data with arespective priority level; storing the plurality of data in a priorityqueue according to the respective priority levels; storing a first datain a data store prior to storing the first data in the priority queue ifthe priority queue is full and if each stored data in the priority queueis tagged with a higher priority level; moving a stored data tagged witha lower priority level from the priority queue to the data store if thepriority queue is full and if the first data is tagged with a higherpriority level; selecting a medium to present the first data of theplurality of data to a user; and presenting the first data to the uservia the medium, wherein the plurality of nodes includes a remote nodeand an in-vehicle device.
 7. The logic of claim 6, wherein the taggingeach of the plurality of data with a respective priority levelcomprises: identifying a data type of the first data of the plurality ofdata; accessing a previously stored mapping of data types tocorresponding priority levels; and associating a priority level to thefirst data, the priority level corresponding to the data type of thefirst data.
 8. The logic of claim 7, wherein the previously storedmapping of data types may be set by a user preference.
 9. The logic ofclaim 6, wherein the code for execution, when executed by a processor isoperable to perform further operations comprising: determining that afirst information of the first data and a second information of a seconddata are related; and combining the first data containing the firstinformation with the second data containing the second information intoa combined data, wherein the combined data is ordered in the priorityqueue.
 10. The logic of claim 6, wherein the in-vehicle device is asensor in the vehicle, wherein the remote node is a second on-board unitof a second vehicle.
 11. An apparatus, comprising: a memory elementconfigured to store data; a network interface; and a computing processoroperable to execute instructions associated with the data, wherein thenetwork interface, computing processor, and the memory element cooperatesuch that the apparatus is configured for: establishing communicationchannels between the apparatus in a vehicle and a plurality of nodes;receiving a plurality of data from the plurality of nodes; tagging eachof the plurality of data with a respective priority level; storing theplurality of data in a priority queue according to the respectivepriority levels; storing a first data in a data store prior to storingthe first data in the priority queue if the priority queue is full andif each stored data in the priority queue is tagged with a higherpriority level; moving a stored data tagged with a lower priority levelfrom the priority queue to the data store if the priority queue is fulland if the first data is tagged with a higher priority level; selectinga medium to present the first data of the plurality of data to a user;and presenting the first data to the user via the medium, wherein theplurality of nodes includes a remote node and an in-vehicle device. 12.The apparatus of claim 11, wherein the tagging each of the plurality ofdata with a respective priority level comprises: identifying a data typeof the first data of the plurality of data; accessing a previouslystored mapping of data types to corresponding priority levels; andassociating a priority level to the first data, the priority levelcorresponding to the data type of the first data.
 13. The apparatus ofclaim 12, wherein the previously stored mapping of data types may be setby a user preference.
 14. The apparatus of claim 11, wherein theapparatus is further configured for: determining that a firstinformation of the first data and a second information of a second dataare related; and combining the first data containing the firstinformation with the second data containing the second information intoa combined data, wherein the combined data is ordered in the priorityqueue.
 15. The apparatus of claim 11, wherein the in-vehicle device is asensor in the vehicle, wherein the remote node is a second on-board unitof a second vehicle.